Skip to content
Cloud InfrastructureAuto-generatedScore: 28

Security Center MCP Server

The Security Center API, provided by the Microsoft Security (formerly Azure Security Center) resource provider, serves as the programmatic backbone for managing critical security posture and monitoring configurations within an organization's cloud environment.

Quick Start Summary

The Security Center MCP server is a Model Context Protocol bridge that connects AI assistants — including Claude Desktop, Cursor, Windsurf, and VS Code Copilot — to the Security Center API through natural language. It exposes 5 API endpoints as callable tools, such as WorkspaceSettings_List, WorkspaceSettings_Get, WorkspaceSettings_Create, and more. No authentication is required — setup takes approximately 30 seconds. The server uses STDIO transport and can be installed by running npx -y @mcp/azure-com-security-workspacesettings. This integration is sourced from the auto Security Center OpenAPI specification (v2017-08-01-preview) and has a quality score of 28/99 (fair documentation coverage).

5Endpointstools mapped
NoneAuthopen access
28/99Qualityfair
~30 secSetupno auth

Server Details

Category
Cloud Infrastructure
Authentication
None
Endpoints
5 operations
Transport
STDIO
Spec Version
v2017-08-01-preview
Install Command
npx -y @mcp/azure-com-security-workspacesettings

Environment Variables

SECURITY_CENTER_API_KEY

Example: your_security_center_api_key

Top Endpoints

GET
/subscriptions/{subscriptionId}/providers/Microsoft.Security/workspaceSettings

WorkspaceSettings_List

GET
/subscriptions/{subscriptionId}/providers/Microsoft.Security/workspaceSettings/{workspaceSettingName}

WorkspaceSettings_Get

PUT
/subscriptions/{subscriptionId}/providers/Microsoft.Security/workspaceSettings/{workspaceSettingName}

WorkspaceSettings_Create

DELETE
/subscriptions/{subscriptionId}/providers/Microsoft.Security/workspaceSettings/{workspaceSettingName}

WorkspaceSettings_Delete

PATCH
/subscriptions/{subscriptionId}/providers/Microsoft.Security/workspaceSettings/{workspaceSettingName}

WorkspaceSettings_Update

Own this API?

Verify ownership of this listing to control the description, configuration details, and documentation links. Choose between free manual verification or instant premium placement.

Option 1: Free Verification

Slow manual review. Requires creating a GitHub issue with verified documentation or domain verification.

  • • Verified badge on page
  • • Standard search sorting
  • • 2-3 business days review
Start Free Claim →
Instant & Boosted

Option 2: Featured Upgrade($9/mo)

Instant verification plus premium styling, featured badges, and directory placement boost.

  • • ★ Featured star & amber highlight border
  • • Top of directory search placement
  • • Instant activation via claim token

📖 Detailed MCP Integration Guide

A technical breakdown of capabilities, agent workflows, and security/configuration best practices.

Capabilities & Use Cases
The Security Center API, provided by the Microsoft Security (formerly Azure Security Center) resource provider, serves as the programmatic backbone for managing critical security posture and monitoring configurations within an organization's cloud environment. Its core capabilities revolve around the lifecycle management of "workspace settings," which are foundational configurations that dictate how security data—such as security alerts, assessments, and recommendations—is logged, routed, and aggregated. Specifically, these settings define the target Log Analytics workspace for a given subscription, enabling the centralized collection of security telemetry for analysis, visualization in tools like Microsoft Sentinel, and long-term retention. This API is indispensable for enterprise cloud security teams, platform engineers, and DevSecOps practitioners who need to automate the setup and governance of their security monitoring infrastructure, ensuring consistent and compliant logging across multiple subscriptions, especially during account onboarding, migration, or restructuring.
🤖AI Agent Value
When exposed as a suite of tools via the Model Context Protocol (MCP) to an AI coding assistant, this API unlocks a powerful paradigm for intelligent, context-aware infrastructure automation. The primary value is in transforming a static, manual configuration process into a dynamic, conversational, and auditable workflow. An AI agent can leverage these tools to understand the current security logging topology of an organization, make informed recommendations based on best practices, and execute precise changes to implement those recommendations. This integration eliminates the need for developers to memorize complex API structures or manually script routine operations, instead allowing them to focus on high-level security intent. The AI acts as a bridge between human strategy and technical implementation, ensuring that actions are performed correctly and consistently according to the specified API contracts, thereby reducing human error and accelerating response times for security configurations.
💬Example Workflows
In a practical workflow, a developer could instruct an AI coding assistant to perform a series of dynamic, multi-step tasks. For instance, the command "Audit our current workspace settings for all subscriptions and generate a report of which ones are not forwarding data to our central SOC workspace" would prompt the AI to use the GET tools to fetch all configurations, analyze the workspaceId properties, and produce a clear summary. Another instruction might be, "Configure subscription X-Y-Z to send its security data to our new Log Analytics workspace in the EU region," leading the AI to execute a precise PUT operation. The AI could also handle automated compliance checks, responding to "Ensure all subscriptions in the production group have workspace settings enabled and are using our corporate workspace" by verifying and automatically updating any non-compliant settings using the PATCH tool, or even help troubleshoot by diagnosing why data might be missing with a diagnostic query using the GET endpoints.
🛡️Security & Auth
Critical attention to authentication and security is paramount, despite the "None" designation in the specification. In a real-world implementation, this API must be secured using Microsoft Entra ID (formerly Azure Active Directory) with appropriate OAuth 2.0 flows. Developers setting up an MCP server for this API must ensure the service principal or user identity used is granted the最小权限 necessary, typically the "Security Admin" or "Contributor" role scoped specifically to the target subscriptions or resource groups, adhering to the principle of least privilege. The MCP server itself should be configured to securely manage and inject these credentials, never exposing them to the client-side AI assistant. All API calls must be made over HTTPS, and thorough logging of both the tool invocations and the API operations should be maintained for security audit trails. Developers should also validate that the AI's intended actions align with their organization's change management policies before permitting execution.

Similar APIs

Other APIs in the Cloud Infrastructure category.

Related MCP Server Integrations

Supabase API MCP Setup

Manage Supabase projects, databases, authentication, and storage through your AI agent.

Cloud InfrastructureConfigure →

Cloudflare API MCP Setup

Manage Cloudflare DNS, CDN, Workers, and security settings through your AI agent.

Cloud InfrastructureConfigure →

Vercel API MCP Setup

Deploy projects, manage domains, and monitor deployments through your AI agent.

Cloud InfrastructureConfigure →

DigitalOcean API MCP Setup

The DigitalOcean API is a comprehensive, RESTful interface provided by DigitalOcean, a leading cloud infrastructure provider focused on simplifying cloud computing for developers, startups, and enterprises. It serves as the programmatic backbone for managing the entire DigitalOcean ecosystem, enabling users to provision, configure, and control cloud resources such as Droplets (virtual private servers), Kubernetes clusters, managed databases, networks, storage volumes, and application platforms. Core capabilities include full lifecycle management of these resources, from creation and scaling to monitoring and deletion, mirroring the functionality available in the DigitalOcean control panel. Its primary use cases range from automating infrastructure setup for CI/CD pipelines and enabling infrastructure-as-code practices to supporting dynamic application scaling and resource optimization for SaaS products, e-commerce sites, and development environments. The API is designed for both developers seeking to automate their cloud operations and businesses that require programmable, scalable cloud infrastructure without the complexity of larger hyperscale providers.

Cloud InfrastructureConfigure →

Access Analyzer MCP Setup

The AWS Identity and Access Management Access Analyzer API provides a powerful, policy-as-code service that automatically identifies resources accessible from outside your AWS account or organization. At its core, the service continuously evaluates resource-based policies—such as Amazon S3 bucket policies, AWS Identity and Access Management (IAM) roles, Amazon KMS key policies, and AWS Lambda function policies—using logic-based reasoning to determine which resources grant access to unknown external principals. Its primary use case is for security and compliance teams within enterprises to proactively detect unintended data exposure, enforce least privilege principles, and audit cross-account and cross-service access. The API endpoints allow programmatic control to create, configure, and query analyzers, manage archive rules for storing findings, and generate custom policy documents, making it a foundational tool for automating cloud security posture management at scale.

Cloud InfrastructureConfigure →