cosmosdb-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@cosmosdb-mcp list containers in database 'orders' on account 'my-cosmos-account'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Azure Cosmos DB MCP Server
An MCP (Model Context Protocol) server for Azure Cosmos DB. Compatible with any MCP client — Claude Code, Claude Desktop, Cursor, and others.
Exposes tools for listing accounts, databases, and containers, running SQL queries, reading and writing documents, and deleting items. The built-in Azure MCP server that ships with Claude Code provides limited Cosmos DB support — this project covers the full data plane, including writes.
Authentication uses DefaultAzureCredential, which picks up an active az login session automatically. Alternatively, a key can be provided via the AZURE_COSMOS_KEY environment variable. No secrets or keys are ever passed as tool arguments.
Requirements
Related MCP server: SQL Server MCP Server
Installation
Install uv and the Azure CLI if you don't have them:
macOS
brew install uv azure-cliLinux
curl -LsSf https://astral.sh/uv/install.sh | sh
curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash # Debian/UbuntuFor other Linux distributions see the Azure CLI install docs.
Windows
winget install --id=astral-sh.uv
winget install --id=Microsoft.AzureCLIConfiguration
Claude Code users:
claude mcp add --scope user cosmosdb -- uvx cosmosdb-mcpFor other MCP clients, add the following to your server configuration:
{
"mcpServers": {
"cosmosdb": {
"command": "uvx",
"args": ["cosmosdb-mcp"]
}
}
}Restart your MCP client after adding the server. No environment variables are required if you are authenticated with az login. Optional env vars:
AZURE_SUBSCRIPTION_ID— used bycosmosdb_list_accountsif setAZURE_COSMOS_KEY— use instead ofaz loginfor data plane operations
Installing from source
git clone https://github.com/BrianDeacon/cosmosdb-mcp
cd cosmosdb-mcp
uv sync
az loginThen configure with the cloned path:
{
"mcpServers": {
"cosmosdb": {
"command": "uv",
"args": ["run", "--directory", "/path/to/cosmosdb-mcp", "cosmosdb-mcp"]
}
}
}Tools
The account parameter accepts either a short account name (e.g. my-cosmos-account) or a full endpoint URL (e.g. https://my-cosmos-account.documents.azure.com). The prefix and suffix are added automatically if absent.
cosmosdb_list_accounts
List all Cosmos DB accounts in the current Azure subscription. The subscription is resolved automatically — first from the AZURE_SUBSCRIPTION_ID environment variable, then from the active az login session.
cosmosdb_list_databases
Parameter | Type | Required | Description |
| string | yes | Cosmos DB account name or endpoint |
Returns a sorted JSON array of database names.
cosmosdb_list_containers
Parameter | Type | Required | Description |
| string | yes | Cosmos DB account name or endpoint |
| string | yes | Database name |
Returns a sorted JSON array of container names.
cosmosdb_get_container_info
Parameter | Type | Required | Description |
| string | yes | Cosmos DB account name or endpoint |
| string | yes | Database name |
| string | yes | Container name |
Returns partition key path, indexing policy, default TTL, unique key policy, and system properties.
cosmosdb_query_items
Parameter | Type | Required | Description |
| string | yes | Cosmos DB account name or endpoint |
| string | yes | Database name |
| string | yes | Container name |
| string | yes | SQL query (e.g. |
| integer | no | Max items to return (default 100, cap 1000) |
Cross-partition queries are enabled automatically. Use cosmosdb_query_items_to_file instead if the result set may be large.
cosmosdb_query_items_to_file
Same as cosmosdb_query_items but writes results to a file. Only the item count is returned in context, avoiding large payloads filling the context window.
Parameter | Type | Required | Description |
| string | yes | Cosmos DB account name or endpoint |
| string | yes | Database name |
| string | yes | Container name |
| string | yes | SQL query |
| string | yes | Path to write results as a JSON array |
| integer | no | Max items to return (default 100, cap 1000) |
cosmosdb_count_items
Parameter | Type | Required | Description |
| string | yes | Cosmos DB account name or endpoint |
| string | yes | Database name |
| string | yes | Container name |
| string | no | SQL WHERE clause body (e.g. |
Returns a JSON object with a count field.
cosmosdb_read_item
Parameter | Type | Required | Description |
| string | yes | Cosmos DB account name or endpoint |
| string | yes | Database name |
| string | yes | Container name |
| string | yes | Item |
| string | yes | Partition key value |
Returns the full item document as JSON.
cosmosdb_upsert_item
Parameter | Type | Required | Description |
| string | yes | Cosmos DB account name or endpoint |
| string | yes | Database name |
| string | yes | Container name |
| object | yes | Full item document — must include an |
Inserts or replaces the item. Returns the stored document including system fields.
cosmosdb_delete_item
Destructive. Deletes an item permanently.
Parameter | Type | Required | Description |
| string | yes | Cosmos DB account name or endpoint |
| string | yes | Database name |
| string | yes | Container name |
| string | yes | Item |
| string | yes | Partition key value |
Security
Authentication relies on
DefaultAzureCredentialorAZURE_COSMOS_KEY— keys are never passed as tool arguments, so secrets do not appear in conversation history.The
accountparameter only accepts account names and endpoint URLs, never connection strings.
Available Tools
10 toolscosmosdb_count_itemsA
Count items in a Cosmos DB container, with an optional filter.
where accepts a SQL WHERE clause body (without the WHERE keyword), e.g.: c.status = 'active' c.createdAt > '2025-01-01'
If where is omitted, counts all items in the container. Returns a JSON object with a 'count' field.
Inputs: account (required), database (required), container (required), where. Returns: result
cosmosdb_delete_itemA
Delete an item from a Cosmos DB container.
THIS IS DESTRUCTIVE — the item cannot be recovered after deletion. Both item_id and partition_key are required.
Inputs: account (required), database (required), container (required), item_id (required), +1 more. Returns: result
cosmosdb_get_container_infoA
Get metadata for a Cosmos DB container.
Returns partition key path, indexing policy, default TTL, unique key policy, and system properties (_self, _etag, _ts). The account can be given as a short name or full endpoint URL.
Inputs: account (required), database (required), container (required). Returns: result
cosmosdb_list_accountsA
List all Azure Cosmos DB accounts in the current subscription.
The subscription is resolved automatically — first from the AZURE_SUBSCRIPTION_ID environment variable, then from the active 'az login' session. If neither is available, an error is returned with instructions.
Inputs: no named parameters. Returns: result
cosmosdb_list_containersA
List all containers in a Cosmos DB database.
Returns a sorted JSON array of container names. The account can be given as a short name or full endpoint URL.
Inputs: account (required), database (required). Returns: result
cosmosdb_list_databasesA
List all databases in an Azure Cosmos DB account.
Returns a sorted JSON array of database names. The account can be given as a short name (e.g. my-cosmos-account) or as a full endpoint URL — the https:// prefix and .documents.azure.com:443/ suffix will be added automatically if missing.
Inputs: account (required). Returns: result
cosmosdb_query_itemsA
Run a SQL query against a Cosmos DB container and return results.
Uses Cosmos DB SQL API syntax, e.g.: SELECT * FROM c WHERE c.status = 'active' SELECT c.id, c.name FROM c ORDER BY c._ts DESC
max_items is capped at 1000. Cross-partition queries are enabled automatically. Use cosmosdb_query_items_to_file instead if the result set may be large.
Inputs: account (required), database (required), container (required), query (required), +1 more. Returns: result
cosmosdb_query_items_to_fileA
Run a SQL query against a Cosmos DB container and save results to a file.
Results are written to output_file as a JSON array. Only the item count is returned in context — use this variant when the result set may be large to avoid filling the context window. max_items is capped at 1000.
Inputs: account (required), database (required), container (required), query (required), +2 more. Returns: result
cosmosdb_read_itemA
Read a single item from a Cosmos DB container by ID and partition key.
Returns the full item document as JSON. Both item_id and partition_key are required — Cosmos DB requires the partition key for efficient point reads.
Inputs: account (required), database (required), container (required), item_id (required), +1 more. Returns: result
cosmosdb_upsert_itemA
Insert or replace an item in a Cosmos DB container.
The item must include an 'id' field. If an item with the same id and partition key already exists it will be replaced; otherwise a new item is created. Returns the stored item document (including system fields) as JSON.
Inputs: account (required), database (required), container (required), item (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
Each tool targets a distinct resource or operation: count, delete, container info, account/database/container listing, query (with two variants for output), read, and upsert. No overlaps.
All tools follow a consistent 'cosmosdb_verb_noun' pattern in snake_case, e.g., list_databases, query_items, upsert_item. Even the longer query_items_to_file is internally consistent.
10 tools is well-scoped for a Cosmos DB server, covering listing, CRUD, query, and metadata operations without being excessive or sparse.
Covers account/database/container listing, item CRUD (read, upsert, delete), query, and count. Minor gap: no explicit update item, but upsert covers replacement. Overall solid for typical usage.
Maintenance
Related MCP Connectors
An MCP server that provides read access to your cloud storage providers, bank accounts and more.
The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.
MCP server for interacting with the Supabase platform
Hosted SQL Server MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Related MCP Servers
- AlicenseBqualityDmaintenanceAn MCP server that provides access to Azure Data Explorer (ADX) clusters, allowing users to list tables, execute queries, and retrieve schema information.71MIT
- AlicenseNot gradedqualityDmaintenanceA containerized Model Context Protocol server for SQL Server operations, enabling query execution, table management, and database operations through the MCP protocol.1MIT
- AlicenseAqualityDmaintenanceAn MCP server for Azure development and operations, enabling Cosmos DB queries, Service Bus messaging, and PIM role activation.3128 PyPIMIT
- FlicenseNot gradedqualityDmaintenanceThis MCP server enables querying Azure resource pricing programmatically through a structured workflow, including listing service families, service names, products, and calculating monthly costs.-