Azure MCP
Wraps the Azure CLI surface — resource groups, storage, Cosmos DB, Key Vault — so an agent can inspect a subscription and propose commands with the real names in them.
What it does
Wraps the Azure CLI surface — resource groups, storage, Cosmos DB, Key Vault — so an agent can inspect a subscription and propose commands with the real names in them. The value is accuracy of identifiers, not autonomy. Authenticate with a scoped service principal: an agent holding your personal credentials can delete things you forgot existed.
Install
npx -y @azure/mcp
Client configuration
Paste this into your MCP client config (Claude Desktop, Cursor, or any client that reads mcpServers), then restart the client.
{
"mcpServers": {
"azure": {
"command": "npx",
"args": [
"-y",
"@azure/mcp"
]
}
}
}
Use it for
Reading Azure resource state and generating CLI commands against a real subscription
Skip it if
Anything outside Azure; and anything you would not hand a service principal
When to use it
Reach for this when the task needs azure inside the agent loop. Skip it if a plain shell command or a one-off script is enough — every server you add costs context and adds a failure mode.
Other TypeScript servers
- Filesystem — Gives an agent scoped read, write, and search access to directories you explicitly allow
- Memory — A persistent knowledge graph stored in a local JSON file, exposed through entities, relations, and observations
- Sequential Thinking — Gives the model a scratchpad for structured, revisable reasoning: numbered thoughts that can branch, revise, and conclude