Skip to content
Cloud InfrastructureAuto-generatedScore: 28

Security Center MCP Server

The Microsoft Security Center API provides programmatic access to the Advanced Threat Protection settings for resources within an Azure subscription, offered as part of 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 2 API endpoints as callable tools, such as AdvancedThreatProtection_Get, AdvancedThreatProtection_Create. 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-advancedthreatprotectionsettings. 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).

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

Server Details

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

Environment Variables

SECURITY_CENTER_API_KEY

Example: your_security_center_api_key

Top Endpoints

GET
/{resourceId}/providers/Microsoft.Security/advancedThreatProtectionSettings/{settingName}

AdvancedThreatProtection_Get

PUT
/{resourceId}/providers/Microsoft.Security/advancedThreatProtectionSettings/{settingName}

AdvancedThreatProtection_Create

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 Microsoft Security Center API provides programmatic access to the Advanced Threat Protection settings for resources within an Azure subscription, offered as part of the Microsoft.Security resource provider. This API is a critical component of the broader Microsoft Defender for Cloud ecosystem, enabling organizations to configure and manage a core layer of their cloud security posture management (CSPM) and workload protection strategies. Its primary function is to allow the retrieval and configuration of the advancedThreatProtectionSettings for a specified resource, such as a virtual machine, SQL database, or storage account. By leveraging the GET and PUT operations on the /{resourceId}/providers/Microsoft.Security/advancedThreatProtectionSettings/{settingName} endpoint, security administrators and automated systems can query the current state of threat protection (e.g., enabled or disabled) for a specific resource and, crucially, update this setting to enforce security policies at scale. The typical enterprise use case involves centralizing the management of ATP policies to ensure consistent protection across all eligible resources, automating security hardening for newly deployed infrastructure, and auditing configurations for compliance against internal standards or external regulations.
🤖AI Agent Value
Exposing this API as a tool within an AI coding assistant via the Model Context Protocol (MCP) transforms it from a management endpoint into an active participant in the developer and security engineer's workflow. The core value lies in enabling AI agents to operate with direct, contextual awareness of a resource's security configuration state within the live Azure environment. Instead of manually writing scripts or clicking through the portal, a developer can engage in natural language dialogue to perform critical security operations. The AI assistant, powered by the MCP server, can dynamically interpret the underlying API to fetch real-time data or effect changes. This integration turns abstract security policies into actionable, conversational commands, significantly accelerating the configuration management lifecycle and reducing the cognitive load associated with navigating complex cloud security toolchains.
💬Example Workflows
In practice, a developer or security engineer can instruct the AI agent to perform a variety of dynamic, context-aware tasks. For example, one could issue a command like, "Check if Advanced Threat Protection is enabled for the production database 'db-prod-01' and enable it if it's not." The AI agent would then use the GET endpoint to query the current setting, interpret the response, and if necessary, invoke the PUT endpoint to apply the desired configuration. Another powerful workflow involves bulk operations and audit reporting; a user could ask, "Generate a report of all Azure SQL databases in the 'eastus' resource group and their ATP status," prompting the AI agent to iterate through resources, collect the data via multiple API calls, and synthesize the findings into a coherent summary. Furthermore, it can be used for policy enforcement automation, where a user might state, "Ensure all storage accounts in our development environment have ATP disabled," allowing the agent to identify targets and execute the necessary state changes, effectively acting as a natural language interface for security policy codification and enforcement.
🛡️Security & Auth
Critical to the safe and effective implementation of this API through an MCP server are robust authentication and authorization protocols, despite the spec listing the method as "None." In a real-world Azure deployment, these operations are protected by Azure Active Directory and require an OAuth 2.0 bearer token with sufficient permissions. Developers must configure the MCP server to securely handle Azure credentials, typically using a service principal with a narrowly scoped RBAC role such as "Security Admin" or a custom role with the Microsoft.Security/advancedThreatProtectionSettings/write permission. Adhering to the principle of least privilege is paramount; the service principal should only be granted access to the specific resource groups or subscriptions requiring management. The MCP server itself must be deployed in a trusted environment, with all tokens and secrets managed securely via Azure Key Vault or similar secret management solutions, ensuring that automated security policy management does not itself become a security vulnerability.

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 →