Azure for cloud infrastructure
Microsoft's official Azure MCP server is the third of four picks for managing cloud infrastructure from an agent, and the reason is simple: it is the natural fit only if your systems run on Azure. For a Microsoft-cloud shop it is the obvious choice, connecting an agent to 40-plus Azure services through purpose-built tools rather than a single shell.
It ranks third here because the field is led by the clouds more teams run on, but for an Azure estate that ranking inverts. The server speaks Azure's own resource model directly, so an agent can inspect storage, query a database, read monitoring logs, and operate managed services without you mapping each request onto raw CLI syntax.
How Azure fits
The tool set is broad and service-shaped. storage manages accounts, blob containers, blobs, queues, and tables. cosmos, sql, mysql, postgres, and redis each operate their managed database service, including queries against Cosmos and SQL. monitor runs KQL against Log Analytics and reads metrics, while applicationinsights and workbooks cover app telemetry and reporting. keyvault lists and creates keys, secrets, and certificates, with secret retrieval gated behind a confirmation step. appconfig handles centralized settings and feature flags, and aks lists Kubernetes clusters. That spread lets one agent move from a database to the secret it needs to the monitor that watches it.
The honest limit is the boundary: this server is Azure only. If your infrastructure lives on AWS, the AWS Labs server fits better; for Google Cloud, Google Cloud Run is the match. Cloudflare is the pick for the edge layer (DNS, Workers, R2) that often fronts an Azure backend rather than living inside it. Within Azure, the per-service tools here give an agent more structured reach than a generic cloud shell would.
Tools you would use
| Tool | What it does |
|---|---|
| storage | Manage Azure Storage accounts, blob containers, blobs, queues, and tables. |
| keyvault | List and create keys, secrets, and certificates in Azure Key Vault (secret retrieval is gated by a confirmation step). |
| cosmos | Work with Azure Cosmos DB accounts, databases, containers, and documents, including queries. |
| sql | Work with Azure SQL Database servers, databases, firewall rules, elastic pools, and Entra admins. |
| mysql | Manage Azure Database for MySQL servers, databases, and tables. |
| postgres | Manage Azure Database for PostgreSQL servers, databases, and tables. |
| redis | Create and list Azure Managed Redis and Azure Cache for Redis resources. |
| monitor | Query Azure Monitor logs (KQL against Log Analytics) and metrics. |
| workbooks | Create, manage, and update Azure Workbooks for data visualization and reporting. |
| appconfig | Manage centralized application settings and feature flags in Azure App Configuration. |
FAQ
- Which Azure services can the agent actually touch?
- The server exposes tools for storage, Key Vault, Cosmos DB, Azure SQL, MySQL, PostgreSQL, Redis, Monitor, Application Insights, Workbooks, App Configuration, and AKS, among the 40-plus services it covers. Database tools like cosmos and sql run queries as well as management calls.
- Can the agent read secrets out of Key Vault?
- It can, but secret retrieval through the keyvault tool is gated by a confirmation step, so the agent cannot silently pull a secret. It can list and create keys, secrets, and certificates more freely; reading a secret value requires that extra confirmation.