Azure Security - AutomationsMCP Configuration & Schema Registry
The Azure Security - Automations Model Context Protocol (MCP) configuration provides a validated, machine-readable JSON schema and executable bridge that connects state-of-the-art AI coding assistants — including Claude Desktop, Cursor IDE, Windsurf, Cline, and VS Code Copilot — directly to the Azure Security - Automations REST API. By leveraging the standardized open Model Context Protocol, AI agents can dynamically discover capabilities, validate input parameters against strict JSON Schemas, and execute live API operations without context switching or manual copy-pasting.
Quick Specs & Integration Summary
Technical Architecture & Protocol Semantics
Under the Model Context Protocol specification, the Azure Security - Automations configuration functions as an isolated protocol adapter. When an AI agent initializes a session, the client establishes a bidirectional JSON-RPC 2.0 communication channel over standard input/output (stdio) or Server-Sent Events (SSE). During the initial handshake, the server publishes its tool manifest extracted from the Azure Security - Automations OpenAPI specification (version 2019-01-01-preview).
The Security Center API, provided by Microsoft as part of its Azure cloud platform, serves as the foundational interface for managing and orchestrating security automation within the Microsoft Defender for Cloud ecosystem. Its core capability is to programmatically control "Automation Rules," which are predefined response actions triggered automatically by security alerts, recommendations, or other events detected across an organization's Azure resources. For enterprise security operations (SecOps) and DevOps teams, this API enables the codification of incident response playbooks, ensuring consistent, rapid, and scalable remediation of threats—for example, automatically isolating a compromised virtual machine, rotating credentials, or triggering a remediation deployment when a critical vulnerability is identified. It transforms reactive security procedures into automated, auditable workflows integrated directly into cloud infrastructure management. Exposing this API as a set of tools via the Model Context Protocol (MCP) to an AI coding assistant unlocks significant efficiency and intelligence in cloud security management. Instead of manually writing infrastructure-as-code templates or navigating the Azure Portal, a developer or security engineer can engage in natural language conversation with an AI agent to perform complex automation lifecycle management. The AI can interpret high-level security policy intent and translate it directly into the appropriate API calls, effectively acting as an expert pair programmer for cloud security. This integration allows the AI to serve as a knowledgeable intermediary, reducing the learning curve for complex API schemas, minimizing configuration errors, and accelerating the implementation of security governance through automation. In a practical workflow, a developer could instruct an MCP-connected AI agent with tasks such as, "List all existing security automations in subscription X to audit our current automated response coverage," to which the agent would use the GET endpoints to retrieve and summarize the configurations. Further, a command like, "Create a new automation named 'Critical-VM-Isolation' in resource group 'SecOps-RG' that triggers on critical alerts and calls an Azure Function to isolate the affected VM," would prompt the AI to construct the necessary JSON payload and execute the PUT endpoint. The agent could also be directed to "Validate the configuration of my staging automation before deploying it to production," using the POST /validate endpoint to check for errors without applying changes. This dynamic capability allows for iterative development, testing, and deployment of security automation policies through conversational interaction. Critical to the use of this API is its authentication requirement, which mandates valid Azure Active Directory (Azure AD) tokens. Although the API specification itself does not define the authentication flow, developers must implement proper OAuth 2.0 bearer token acquisition within their MCP server integration. Adherence to the principle of least privilege is paramount; the service principal or user account utilized must be granted the specific Azure RBAC role "Security Admin" or "Contributor" at the appropriate scope (subscription or resource group), and no broader permissions. Configuration must also ensure that tokens are never exposed in logs, are securely managed, and that the MCP server endpoint itself is protected. Best practices include using managed identities where possible, implementing token caching, and rigorously validating all inputs to the automation creation and update endpoints to prevent injection attacks or misconfiguration that could inadvertently disable security monitoring. This architecture guarantees strict process boundary isolation: all sensitive authorization headers and secret tokens remain sandboxed inside the client runtime, never leaking into language model context windows or external logging endpoints.
Hosted Remote Configuration URL
MCP Configuration FileProvide this hosted URL in any client that supports remote MCP schema auto-loading.
https://mcpbridge.org/config/azure-com-security-automations.json2. AI Assistant Use Cases & Practical Workflows
Tailored for Cloud InfrastructureReal-world execution scenarios demonstrating how LLM agents (Claude 3.7, GPT-4o, Cursor Agent) invoke Azure Security - Automations tools to automate developer workflows.
1. CI/CD Build Failure & Telemetry Diagnostics
CI/CD RemediationInstantly diagnose failing CI/CD builds or deployment pipelines by streaming build logs, isolating failure root causes, and drafting targeted code fixes.
"Fetch recent pipeline run logs from Azure Security - Automations. Isolate the failed step, summarize the exact compiler or test failure error, and propose a pull request fix in Cursor."
2. Cloud Resource Auditing & Cost Optimization
Cloud FinOpsScan active compute clusters, storage buckets, and networking configurations to identify unattached volumes or idle oversized instances.
"Query active cloud infrastructure resources in Azure Security - Automations. Identify unattached storage volumes, idle compute instances, and summarize estimated monthly cost savings."
3. Zero-Downtime Rollout & Canary Health Verification
Deployment OpsOrchestrate progressive deployments, monitor error rate thresholds on newly deployed pods, and execute automated rollbacks if error budgets breach.
"Check the active deployment rollout status in Azure Security - Automations. Monitor canary error rate percentages for 5 minutes and report whether the deployment is safe to promote to 100% traffic."
4. Infrastructure as Code (IaC) Drift Detection
IaC GovernanceCompare live deployed resource state against Terraform or CloudFormation definitions to spot unauthorized manual changes.
"Scan live configurations via Azure Security - Automations and compare against our repository IaC definitions. Highlight any configuration drift in security groups or network routes."
End-to-End Multi-Step Agent Execution Lifecycle
When an engineer submits a task to Claude Desktop or Cursor, the LLM executes an autonomous 4-phase Model Context Protocol loop:
Schema Introspection
Handshake lists all 6 tools and builds argument validators.
Argument Synthesis
Model extracts parameters from prompt and validates types against OpenAPI rules.
Stdio Execution
Bridge invokes live API with injected local credentials and captures raw HTTP response.
Output Remediation
LLM parses JSON results, handles status codes, and presents synthesized answers.
3. Multi-Client Installation Matrix & Setup Guides
Select your AI assistant below to view exact configuration file paths, JSON installation snippets, and launch commands.
Claude Desktop
claude_desktop_config.json~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.json{
"mcpServers": {
"azure-com-security-automations": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-openapi",
"https://api.apis.guru/v2/specs/azure.com/security-automations/2019-01-01-preview/swagger.json"
],
"env": {
"SECURITY_CENTER_API_KEY": "your_security_center_api_key"
}
}
}
}Cursor IDE
.cursor/mcp.jsonOpen Cursor Settings → Features → MCP Servers, or create .cursor/mcp.json in your project root.
{
"mcpServers": {
"azure-com-security-automations": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-openapi",
"https://api.apis.guru/v2/specs/azure.com/security-automations/2019-01-01-preview/swagger.json"
],
"env": {
"SECURITY_CENTER_API_KEY": "your_security_center_api_key"
}
}
}
}Saves as .cursor/mcp.json in the download. Move it to your project root.
VS Code / Cline Extension
cline_mcp_settings.jsonPaste into your Cline extension MCP configuration or Roo Code host settings.
{
"mcpServers": {
"azure-com-security-automations": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-openapi",
"https://api.apis.guru/v2/specs/azure.com/security-automations/2019-01-01-preview/swagger.json"
],
"env": {
"SECURITY_CENTER_API_KEY": "your_security_center_api_key"
}
}
}
}Zed Editor & Docker CLI
Zed / DockerDocker container execution command:
docker run -i --rm -e SECURITY_CENTER_API_KEY="YOUR_SECRET_VALUE" node:20-alpine npx -y @modelcontextprotocol/server-openapi https://api.apis.guru/v2/specs/azure.com/security-automations/2019-01-01-preview/swagger.json
Zed settings context servers JSON:
{
"context_servers": {
"azure-com-security-automations": {
"command": {
"path": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-openapi",
"https://api.apis.guru/v2/specs/azure.com/security-automations/2019-01-01-preview/swagger.json"
],
"env": {
"SECURITY_CENTER_API_KEY": "your_security_center_api_key"
}
}
}
}
}Programmatic SDK Integration (TypeScript / Python)
Initialize the Azure Security - Automations MCP client directly in your backend codebase.
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StdioClientTransport } from "@modelcontextprotocol/sdk/client/stdio.js";
// Initialize Azure Security - Automations MCP client transport over stdio
const transport = new StdioClientTransport({
command: "npx",
args: ["-y","@modelcontextprotocol/server-openapi","https://api.apis.guru/v2/specs/azure.com/security-automations/2019-01-01-preview/swagger.json"],
env: { SECURITY_CENTER_API_KEY: process.env.SECURITY_CENTER_API_KEY || "YOUR_SECRET_KEY" }
});
const client = new Client(
{ name: "azure-com-security-automations-client", version: "1.0.0" },
{ capabilities: { tools: {}, resources: {}, prompts: {} } }
);
async function connectAndRun() {
await client.connect(transport);
const tools = await client.listTools();
console.log("Connected to Azure Security - Automations MCP Server.");
console.log("Discovered 6 mapped tools:", tools);
}
connectAndRun().catch(console.error);Raw Stdio Schema Definition
schema.jsonFor standalone CLI wrappers, background daemon daemons, or custom script integrations:
{
"mcpServers": {
"azure-com-security-automations": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-openapi",
"https://api.apis.guru/v2/specs/azure.com/security-automations/2019-01-01-preview/swagger.json"
],
"env": {
"SECURITY_CENTER_API_KEY": "your_security_center_api_key"
}
}
}
}4. Security, Authentication & Credential Management
Safely configure authentication tokens, isolate execution environments, and implement enterprise security best practices.
Required Environment Keys Reference
| Variable Name | Required | Type | Default | Purpose & Guidance |
|---|---|---|---|---|
| SECURITY_CENTER_API_KEY | REQUIRED | Secret Key / Token | None (Set in env) | your_security_center_api_key |
Zero-Downtime Token Rotation Protocol
- Generate Secondary Key: Create a new secret API token with identical scopes in your Azure Security - Automations developer portal.
- Update Client Configuration: Insert the new token inside the
envblock of your MCP client JSON config. - Validate Connection: Issue a test query in Claude or Cursor to ensure handshake and tool calls succeed.
- Revoke Stale Token: Decommission the legacy key on the vendor portal to prevent unauthorized access.
Least-Privilege & Sandboxing Rules
- Read-Only Token Scoping: Whenever your workflow only requires querying data, provision read-only credentials to prevent accidental mutations.
- Local Process Isolation: Stdio transports run in isolated local subprocesses; secret credentials are never sent across the internet to MCP Bridge servers.
- Prompt Injection Defense: AI model responses are sandboxed; verify generated destructive arguments before confirming execution in agent mode.
Enterprise Security Checklist (Mandatory Practices)
- Never commit
claude_desktop_config.jsonor.cursor/mcp.jsoncontaining raw secrets into public GitHub repositories. - Add
.cursor/mcp.jsonand.env.localto your project's.gitignorefile. - Always enforce TLS/HTTPS encryption on outbound network requests initiated by the server process.
5. Tool Parameter Schemas & Natural Language Execution
Mapped OpenAPI operations converted into discrete Model Context Protocol tools with strict JSON-RPC payload validators.
/subscriptions/{subscriptionId}/providers/Microsoft.Security/automationsAutomations_List
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "azure-com-security-automations_get_subscriptions__subscriptionId__providers_Microsoft_Security_automations",
"arguments": {}
}
}"Use Azure Security - Automations to execute Automations_List and output the formatted result."
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Security/automationsAutomations_ListByResourceGroup
{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "azure-com-security-automations_get_subscriptions__subscriptionId__resourceGroups__resourceGroupName__providers_Microsoft_Security_automations",
"arguments": {}
}
}"Use Azure Security - Automations to execute Automations_ListByResourceGroup and output the formatted result."
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Security/automations/{automationName}Automations_Get
{
"jsonrpc": "2.0",
"id": 3,
"method": "tools/call",
"params": {
"name": "azure-com-security-automations_get_subscriptions__subscriptionId__resourceGroups__resourceGroupName__providers_Microsoft_Security_automations__automationName",
"arguments": {}
}
}"Use Azure Security - Automations to execute Automations_Get and output the formatted result."
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Security/automations/{automationName}Automations_CreateOrUpdate
{
"jsonrpc": "2.0",
"id": 4,
"method": "tools/call",
"params": {
"name": "azure-com-security-automations_put_subscriptions__subscriptionId__resourceGroups__resourceGroupName__providers_Microsoft_Security_automations__automationName",
"arguments": {}
}
}"Use Azure Security - Automations to execute Automations_CreateOrUpdate and output the formatted result."
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Security/automations/{automationName}Automations_Delete
{
"jsonrpc": "2.0",
"id": 5,
"method": "tools/call",
"params": {
"name": "azure-com-security-automations_delete_subscriptions__subscriptionId__resourceGroups__resourceGroupName__providers_Microsoft_Security_automations__automationName",
"arguments": {}
}
}"Use Azure Security - Automations to execute Automations_Delete and output the formatted result."
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Security/automations/{automationName}/validateAutomations_Validate
{
"jsonrpc": "2.0",
"id": 6,
"method": "tools/call",
"params": {
"name": "azure-com-security-automations_post_subscriptions__subscriptionId__resourceGroups__resourceGroupName__providers_Microsoft_Security_automations__automationName__validate",
"arguments": {}
}
}"Use Azure Security - Automations to execute Automations_Validate and output the formatted result."
6. Interactive Troubleshooting & FAQ Accordion
Diagnose and resolve common JSON-RPC protocol error codes, connection disconnects, and schema refresh issues.
A 401 Unauthorized response indicates that the upstream Azure Security - Automations API rejected the authentication credential supplied in your MCP client's environment configuration. To resolve this: (1) Verify that your secret token is defined inside the "env" block of claude_desktop_config.json or .cursor/mcp.json rather than hardcoded in the command string. (2) Check whether Azure Security - Automations requires a prefix such as "Bearer <token>" in the authorization header. (3) Confirm that your API key has not expired and has been granted sufficient least-privilege scopes on the Azure Security - Automations developer dashboard.
If your MCP client fails to initialize tools for Azure Security - Automations: (1) Test the bridge launcher command ("npx -y @modelcontextprotocol/server-openapi https://api.apis.guru/v2/specs/azure.com/security-automations/2019-01-01-preview/swagger.json") directly inside your terminal or shell to inspect stdout/stderr diagnostic traces. (2) Verify network connectivity to the schema source (https://api.apis.guru/v2/specs/azure.com/security-automations/2019-01-01-preview/swagger.json). (3) Ensure Node.js (v18+) is installed and accessible in your system PATH. (4) For authenticated APIs, confirm credentials are configured in your client's "env" mapping rather than command arguments.
MCP clients like Claude Desktop and Cursor query the server's tools list ("tools/list") during startup and cache the resulting JSON Schema for the duration of the application session. If new endpoints or parameters are added to Azure Security - Automations: (1) Fully quit and restart Claude Desktop (Cmd+Q on macOS or File > Exit on Windows). (2) In Cursor IDE, navigate to Settings > Features > MCP Servers, toggle the Azure Security - Automations server off and on, or click the refresh icon to re-execute the initialization handshake.
If the AI model hallucinates parameters or fails to invoke a tool automatically: (1) Add explicit system instructions in your project's .cursorrules or Claude project prompt (e.g., "When querying Cloud Infrastructure, always invoke the azure-com-security-automations MCP server tools first"). (2) Ensure parameter types match schema specifications (e.g., passing integers as numbers rather than strings). (3) Check that required parameters marked in Section 5 are not omitted from the model's generated payload.
When the Azure Security - Automations upstream endpoint returns an HTTP 429 Too Many Requests response, the MCP server bubbles the structured error payload back to the AI client over stdio. Modern LLMs like Claude 3.7 and Cursor Agent recognize rate-limiting status codes, inspect the "Retry-After" header if present, and will automatically introduce backoff delays or ask the user before retrying the operation.
The Hosted Config URL (https://mcpbridge.org/config/azure-com-security-automations.json) provides a static, remote JSON schema definition that cloud-native MCP clients can fetch over HTTPS for dynamic discovery. In contrast, local stdio configurations execute a local subprocess on your workstation. Local stdio processes offer maximum security because secret API keys remain strictly on your local machine and never transit third-party proxy servers.
Similar Cloud Infrastructure Configurations
Explore related API bridges with ready-to-use Model Context Protocol schemas.
Supabase API
Cloud InfrastructureManage Supabase projects, databases, authentication, and storage through your AI agent.
https://mcpbridge.org/config/supabase.jsonCloudflare API
Cloud InfrastructureManage Cloudflare DNS, CDN, Workers, and security settings through your AI agent.
https://mcpbridge.org/config/cloudflare.jsonVercel API
Cloud InfrastructureDeploy projects, manage domains, and monitor deployments through your AI agent.
https://mcpbridge.org/config/vercel.jsonDigitalOcean API
Cloud InfrastructureThe 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. When exposed as tools via the Model Context Protocol (MCP) to an AI coding assistant, the DigitalOcean API transforms from a traditional developer tool into a dynamic, context-aware resource for intelligent infrastructure automation. The MCP server acts as a bridge, allowing the AI model to understand and execute API calls based on natural language instructions and the current project context. This integration provides immense value by enabling the AI to perform real-time cloud management tasks directly within the development workflow. For instance, the AI can instantly query account details to verify resources, list and manage SSH keys for secure access, or retrieve and monitor the status of infrastructure actions. This contextual access means the AI can make informed suggestions or take automated actions—like recommending a cost-optimized Droplet size based on current usage patterns or verifying that a new SSH key has been correctly added before proceeding with a deployment script—thereby reducing context-switching and accelerating development cycles. Practical workflow examples demonstrate the power of this MCP integration. A developer could instruct the AI agent with commands like, "Query our account for all active SSH keys and ensure the one named 'ci-bot' is present; if not, create it using this public key," automating a common security and setup step. Another example involves asking the AI to "Check the status of our last ten infrastructure actions to see if any are stuck in a 'pending' state," which would leverage the actions endpoints to provide an immediate operational health check. More complex automations are possible, such as "Based on the current Droplet inventory from the API, generate a Terraform configuration file that replicates this setup," or "Scan our Kubernetes 1-Click apps and suggest one for deploying a new microservice based on the project requirements." These interactions turn the AI into a proactive DevOps partner capable of auditing, reporting, and modifying cloud infrastructure through simple, conversational directives. Critical to the secure operation of this MCP server is rigorous attention to authentication and access control, despite any initial configuration notes indicating "None" for simplicity. In any real-world deployment, authentication via a DigitalOcean Personal Access Token is non-negotiable. This token should be treated as a high-privilege secret. Developers must adhere to the principle of least privilege by creating tokens with the minimum scopes required for the specific tasks—such as read-only access for monitoring or write access only for specific resource types. Best practices include storing tokens in secure environment variables or a secrets manager, never hardcoding them, and ensuring the MCP server configuration does not expose them in logs or client-side code. Furthermore, regular token rotation and monitoring of API activity through DigitalOcean's audit logs are essential to maintain a secure posture when integrating cloud management capabilities directly into AI-assisted development environments.
https://mcpbridge.org/config/digitalocean-com.json