Skip to content
Cloud InfrastructureAuto-generatedScore: 28

Security Center MCP Server

The Security Center API, provided by the Microsoft.

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 SecurityContacts_List, SecurityContacts_Get, SecurityContacts_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-securitycontacts. 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-securitycontacts

Environment Variables

SECURITY_CENTER_API_KEY

Example: your_security_center_api_key

Top Endpoints

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

SecurityContacts_List

GET
/subscriptions/{subscriptionId}/providers/Microsoft.Security/securityContacts/{securityContactName}

SecurityContacts_Get

PUT
/subscriptions/{subscriptionId}/providers/Microsoft.Security/securityContacts/{securityContactName}

SecurityContacts_Create

DELETE
/subscriptions/{subscriptionId}/providers/Microsoft.Security/securityContacts/{securityContactName}

SecurityContacts_Delete

PATCH
/subscriptions/{subscriptionId}/providers/Microsoft.Security/securityContacts/{securityContactName}

SecurityContacts_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 resource provider, is the foundational interface for managing the critical human notification layer within Azure Security Center, now integrated as Microsoft Defender for Cloud. Its primary function is the programmatic administration of security contacts—designated individuals or distribution lists responsible for receiving high-priority security alerts, health notifications, and advisories from across an organization’s Azure estate. This RESTful API enables enterprises to dynamically configure, query, and automate the lifecycle of these vital notification endpoints. Typical use cases are pervasive in cloud governance and security operations: a DevOps team automating the onboarding of a new subscription by programmatically setting contact details, a security operations center (SOC) ensuring global coverage by rotating regional contacts, or an IT administrator auditing and enforcing a consistent contact policy across hundreds of subscriptions to eliminate notification blind spots. The API provides the essential plumbing to bridge automated threat detection with human response, ensuring that critical security intelligence does not remain siloed within systems but reaches the right personnel immediately.
🤖AI Agent Value
When exposed as tools to an AI coding assistant through the Model Context Protocol (MCP), the Security Center API gains profound contextual utility. An AI agent, equipped with these endpoints, transitions from a passive code generator to an active cloud operations partner capable of direct, intent-driven interaction with a live security posture. The value is in the elimination of manual console navigation and syntax lookups, allowing developers to express administrative intent in natural language. The AI can understand the relationship between subscription identifiers and security contact names to perform precise, targeted actions. It can orchestrate multi-step workflows by chaining API calls—first querying existing contacts to check for duplicates before applying a new configuration via PUT, or validating a contact's existence before attempting a PATCH or DELETE operation. This integration transforms the API from a set of discrete HTTP calls into a dynamic, programmable part of the security management fabric, dramatically accelerating configuration, auditing, and remediation tasks.
💬Example Workflows
Practical workflow examples highlight this transformative potential. A developer could instruct the AI agent, "For our production subscription 'prod-eastus-01', list all current security contacts and confirm they include the SOC's pager address '[email protected]'." The AI would invoke the GET endpoints, parse the JSON response, and provide a clear confirmation or report a gap. Following this, the command, "Update the contact named 'PrimarySecurityContact' for subscription 'prod-eastus-01' to also receive email at '[email protected]' and change the phone to '+1-555-0199'," would trigger the AI to use the PUT or PATCH endpoint with the appropriate payload. For cleanup automation, a request like "Scan all our subscriptions and delete any security contact entries that are older than 90 days, based on their lastNotificationTimestamp, and log which ones were removed" would prompt the AI to iterate through a provided list of subscriptions, use the list and get endpoints to gather data, and then execute DELETE calls based on the logic, all while maintaining a coherent audit trail.
🛡️Security & Auth
Robust authentication and security are paramount, despite any simplified listing. In practice, the Azure Resource Manager (ARM) API for Microsoft.Security requires an Azure Active Directory (Azure AD) bearer token with appropriate permissions. The 'None' authentication noted likely refers to the public specification's base reference; in implementation, developers must configure the MCP server with service principal or managed identity credentials. Strict adherence to the principle of least privilege is critical. The security principal should be granted only the minimum required roles, such as 'Security Admin' for full management or more granular custom roles for read-only access on specific subscriptions. Secrets, tokens, and subscription IDs must be managed via a secure vault like Azure Key Vault, never embedded in configuration files. All API interactions should occur over HTTPS, and developers should implement comprehensive logging on the MCP server to track which identities are executing what changes, ensuring accountability and simplifying incident response.

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 →