Azure

Microsoft's official Azure MCP is the most comprehensive cloud integration I've tested. It exposes 40+ Azure services through a single server: storage accounts, App Service deployments, Cosmos DB queries, Azure Monitor metrics, Key Vault secrets, and more. The scope is genuinely impressive. You can ask Claude to list your storage accounts, generate a SAS token, then read a blob, all in one conversation thread without switching contexts. I'd reach for this when I'm troubleshooting production issues or prototyping infrastructure changes. The Azure Monitor integration is particularly useful. You can query logs and metrics in natural language, which beats writing KQL by hand when you're under pressure. Deploying to App Service via chat feels almost too easy: "deploy this container to my staging slot" just works, assuming your service principal has the right permissions. The authentication story is straightforward: create a service principal in Entra ID, grant it appropriate RBAC roles, then drop the tenant ID, client ID, and client secret into your environment. The server handles token refresh automatically. One thing to watch: the service principal needs explicit permissions for every Azure resource type you want to touch. If you forget to grant Storage Blob Data Reader, you'll get cryptic permission errors mid-conversation. The main quirk is that it's a monolith. You get all 40+ services whether you need them or not, which makes the initial setup feel heavier than niche MCPs. The tool list in Claude can get crowded. But if you're already deep in Azure, this is the canonical way to wire your agent into your cloud estate. It's maintained by Microsoft, so it tracks Azure API changes faster than community alternatives. Skip this if you only use one or two Azure services, or if you're on AWS or GCP. The setup overhead isn't worth it for casual use. But if Azure is your primary cloud and you want your agent to be a first-class operator, this is the obvious choice.