Microsoft has shipped the MCP Toolkit for Azure Cosmos DB to general availability, giving developers a standardized way to expose Cosmos DB operations through the Model Context Protocol. If you have been wiring up custom API endpoints every time an AI agent needs to read or write database records, this one is for you.
The MCP Toolkit works as a server that sits between your AI agent runtime and Cosmos DB. Instead of writing custom REST handlers for each agent capability (“get customer by ID”, “search products”, “update order status”), you configure the toolkit once and it exposes those operations as MCP tools that any MCP-compatible client can discover and call. The GA release means it carries the same SLA, support commitment, and production readiness as the rest of Cosmos DB.
For the uninitiated: MCP is an open protocol invented by Anthropic that standardizes how AI models talk to tools and data sources. Think of it as USB-C for AI agents. Before MCP, every integration was bespoke. With MCP, a Claude agent, a Copilot agent, and a Foundry agent all call Cosmos DB through the same interface. The toolkit handles authentication through Azure RBAC, connection pooling, and request batching under the hood.
To get started: deploy the MCP Toolkit Server from the Azure portal into your Cosmos DB account. Configure which collections and operations to expose (read-only query by default, write operations opt-in). Then connect any MCP client — Cursor, Visual Studio Code with GitHub Copilot, or a custom agent runtime — by pointing it at the server endpoint. The full setup takes about 15 minutes if you already have a Cosmos DB instance running.
What this means: MCP toolkits are becoming the standard pattern for database-to-agent connectivity. Cosmos DB is the first Azure data service with an officially supported GA toolkit, but it won’t be the last. If you are building agentic applications that need operational data, stop writing custom API wrappers and start designing around MCP. The protocol is vendor-neutral, so you are not locked into Azure if you change your mind later.
Sources: Azure update announcement, MCP specification.