mcpField
M
Mcp Cosmosdb Sql

Mcp Cosmosdb Sql

Local
github.com/hendrickcastroDatabases1Updated 40w ago

About Mcp Cosmosdb Sql

Mcp Cosmosdb Sql is an MCP server for developers and data analysts working with Azure CosmosDB. It supports multiple connections, container analysis, SQL queries, and document CRUD, with writes disabled by default and configurable per connection.

Key features

  1. 01Manage multiple CosmosDB connections
  2. 02Discover databases and containers
  3. 03Inspect container definitions, stats, and schemas
  4. 04Run parameterized SQL queries
  5. 05Retrieve and filter documents
  6. 06Perform guarded document CRUD

Use cases

  1. 01Inspect container structure and statistics
  2. 02Analyze document schemas
  3. 03Query or filter CosmosDB data
  4. 04Maintain documents when writes are enabled

MCP support

The MCP server exposes connection management, database and container inspection, query, document retrieval, and CRUD tools to clients. Document writes are disabled by default and can be enabled per connection.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"MCPCosmosDB": {
"command": "npx",
"args": [
"-y",
"hendrickcastro/MCPCosmosDB"
],
"env": {
"OCONNSTRING": "<OCONNSTRING>",
"COSMOS_DATABASE_ID": "<COSMOS_DATABASE_ID>"
}
}
}
}
Run commandnpx -y hendrickcastro/MCPCosmosDB
Environment variables to set
OCONNSTRING
COSMOS_DATABASE_ID

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmhendrickcastro/MCPCosmosDB

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

MCP CosmosDB - Azure CosmosDB MCP Server

License: MIT npm version Downloads Node.js Version TypeScript GitHub stars GitHub issues GitHub forks Build Status Coverage Status Azure CosmosDB MCP Protocol Claude Desktop Cursor IDE Trae AI

A comprehensive Model Context Protocol (MCP) server for Azure CosmosDB database operations. This server provides 13 powerful tools for document database analysis, container discovery, data querying, and CRUD operations through the MCP protocol.

✨ Features

  • 🔗 Multi-Connection Support: Manage multiple CosmosDB accounts/databases from a single MCP instance
  • 🔒 Security First: Write operations disabled by default
  • ⚡ High Performance: Connection caching and optimized queries
  • 📊 13 Tools: Complete set of database operations

🚀 Quick Start

Prerequisites
  • Node.js 18+ and npm
  • Azure CosmosDB database with connection string
  • MCP-compatible client (Claude Desktop, Cursor IDE, etc.)

⚙️ Configuration

Configuration Priority

The server supports three configuration methods (in order of priority):

PriorityMethodEnvironment VariableDescription
1️⃣External FileCOSMOS_CONNECTIONS_FILEPath to JSON file with connections array
2️⃣JSON StringCOSMOS_CONNECTIONSInline JSON array of connections
3️⃣Single ConnectionCOSMOS_CONNECTION_STRING + COSMOS_DATABASE_IDLegacy single connection mode
🔒 Security Configuration
VariableDescriptionDefault
DB_ALLOW_MODIFICATIONSEnable/disable write operations (create, update, delete, upsert)false

⚠️ IMPORTANT: By default, all write operations are DISABLED for safety. Set DB_ALLOW_MODIFICATIONS=true only when you need to perform write operations.


📦 Installation Options

Option 1: Multi-Connection with External File (Recommended) ✅

Create a connections file (e.g., cosmos-connections.json):

[
  {
    "id": "production",
    "connectionString": "AccountEndpoint=https://myapp-prod.documents.azure.com:443/;AccountKey=...;",
    "databaseId": "ProductionDB",
    "allowModifications": false,
    "description": "Production database (read-only)"
  },
  {
    "id": "development",
    "connectionString": "AccountEndpoint=https://myapp-dev.documents.azure.com:443/;AccountKey=...;",
    "databaseId": "DevDB",
    "allowModifications": true,
    "description": "Development database"
  },
  {
    "id": "analytics",
    "connectionString": "AccountEndpoint=https://analytics.documents.azure.com:443/;AccountKey=...;",
    "databaseId": "AnalyticsDB",
    "allowModifications": false,
    "description": "Analytics database"
  }
]

Configure your MCP client:

{
  "mcpServers": {
    "cosmosdb": {
      "command": "npx",
      "args": ["-y", "mcpcosmosdb@latest"],
      "env": {
        "COSMOS_CONNECTIONS_FILE": "/path/to/cosmos-connections.json"
      }
    }
  }
}
Option 2: Multi-Connection with Inline JSON
{
  "mcpServers": {
    "cosmosdb": {
      "command": "npx",
      "args": ["-y", "mcpcosmosdb@latest"],
      "env": {
        "COSMOS_CONNECTIONS": "[{\"id\":\"prod\",\"connectionString\":\"AccountEndpoint=https://...\",\"databaseId\":\"ProdDB\",\"allowModifications\":false},{\"id\":\"dev\",\"connectionString\":\"AccountEndpoint=https://...\",\"databaseId\":\"DevDB\",\"allowModifications\":true}]"
      }
    }
  }
}
Option 3: Single Connection (Legacy)

Read-Only Mode (Default - Safe):

{
  "mcpServers": {
    "cosmosdb": {
      "command": "npx",
      "args": ["-y", "mcpcosmosdb@latest"],
      "env": {
        "COSMOS_CONNECTION_STRING": "AccountEndpoint=https://your-cosmos-account.documents.azure.com:443/;AccountKey=your-account-key-here;",
        "COSMOS_DATABASE_ID": "your-database-name"
      }
    }
  }
}

With Write Operations Enabled:

{
  "mcpServers": {
    "cosmosdb": {
      "command": "npx",
      "args": ["-y", "mcpcosmosdb@latest"],
      "env": {
        "COSMOS_CONNECTION_STRING": "AccountEndpoint=https://your-cosmos-account.documents.azure.com:443/;AccountKey=your-account-key-here;",
        "COSMOS_DATABASE_ID": "your-database-name",
        "DB_ALLOW_MODIFICATIONS": "true"
      }
    }
  }
}
Option 4: NPX from GitHub
{
  "mcpServers": {
    "cosmosdb": {
      "command": "npx",
      "args": ["-y", "hendrickcastro/MCPCosmosDB"],
      "env": {
        "COSMOS_CONNECTION_STRING": "AccountEndpoint=https://...;AccountKey=...;",
        "COSMOS_DATABASE_ID": "your-database-name"
      }
    }
  }
}
Option 5: Local Development
git clone https://github.com/hendrickcastro/MCPCosmosDB.git
cd MCPCosmosDB
npm install && npm run build
{
  "mcpServers": {
    "cosmosdb": {
      "command": "node",
      "args": ["path/to/MCPCosmosDB/dist/server.js"],
      "env": {
        "COSMOS_CONNECTIONS_FILE": "/path/to/cosmos-connections.json"
      }
    }
  }
}

🛠️ Available Tools (13 Total)

🔗 Connection Management
ToolDescription
mcp_list_connectionsList all configured connections with their status
📖 Read Operations (Always Available)
ToolDescription
mcp_list_databasesList all databases in the CosmosDB account
mcp_list_containersList all containers in the current database
mcp_get_container_definitionGet detailed container configuration (partition key, indexing policy, throughput)
mcp_get_container_statsGet container statistics (document count, size, partition distribution)
mcp_cosmos_queryExecute SQL queries with parameters and performance metrics
mcp_get_documentsRetrieve documents with optional filtering
mcp_get_document_by_idGet a specific document by ID and partition key
mcp_analyze_schemaAnalyze document schema structure in containers
✏️ Write Operations (Require allowModifications: true)
ToolDescription
mcp_create_documentCreate a new document in a container
mcp_update_documentUpdate (replace) an existing document
mcp_delete_documentDelete a document from a container
mcp_upsert_documentCreate or update a document (upsert operation)

🛡️ Security Note: Write operations are blocked by default. Set allowModifications: true in the connection config or DB_ALLOW_MODIFICATIONS=true for single connection mode.


📋 Usage Examples

Multi-Connection Usage
// List all available connections
const connections = await mcp_list_connections();
// Returns: { connections: [{id: "prod", databaseId: "ProdDB", isConnected: true}, ...] }

// Query specific connection using connection_id
const prodData = await mcp_cosmos_query({
  connection_id: "production",
  container_id: "users",
  query: "SELECT TOP 10 c.id, c.name FROM c ORDER BY c._ts DESC"
});

const devData = await mcp_cosmos_query({
  connection_id: "development",
  container_id: "users",
  query: "SELECT TOP 10 c.id, c.name FROM c ORDER BY c._ts DESC"
});
Container Analysis
// List all containers (uses default connection if connection_id not specified)
const containers = await mcp_list_containers({
  connection_id: "production"
});

// Get container definition
const containerDef = await mcp_get_container_definition({ 
  connection_id: "production",
  container_id: "users" 
});

// Get container statistics
const stats = await mcp_get_container_stats({ 
  connection_id: "production",
  container_id: "users",
  sample_size: 1000
});
Querying Data

⚠️ IMPORTANT: Always use TOP N and specify fields. NEVER use SELECT * - it causes timeouts and high RU consumption in large containers.

// ✅ CORRECT: Using TOP and specific fields
const result = await mcp_cosmos_query({
  connection_id: "production",
  container_id: "products",
  query: "SELECT TOP 50 c.id, c.name, c.price FROM c WHERE c.category = @category",
  parameters: { category: "electronics" }
});

// ❌ WRONG: SELECT * without TOP (will timeout on large containers)
// query: "SELECT * FROM c WHERE c.category = @category"

// Get documents with simple filters
const documents = await mcp_get_documents({
  connection_id: "production",
  container_id: "orders",
  filter_conditions: { status: "completed" },
  order_by: "_ts",
  order_direction: "DESC",
  limit: 100
});
Document Operations
// Get specific document by ID
const document = await mcp_get_document_by_id({
  connection_id: "production",
  container_id: "users",
  document_id: "user-123",
  partition_key: "user-123"
});

// Analyze schema
const schema = await mcp_analyze_schema({
  connection_id: "production",
  container_id: "products",
  sample_size: 500
});
CRUD Operations (Requires allowModifications: true)
// Create a new document
const created = await mcp_create_document({
  connection_id: "development",  // Use a connection with write access
  container_id: "users",
  document: {
    id: "user-456",
    email: "[email protected]",
    name: "John Doe",
    status: "active"
  },
  partition_key: "user-456"
});

// Update a document (full replacement)
const updated = await mcp_update_document({
  connection_id: "development",
  container_id: "users",
  document_id: "user-456",
  document: {
    id: "user-456",
    email: "[email protected]",
    name: "John Doe",
    status: "inactive"
  },
  partition_key: "user-456"
});

// Upsert a document (create or update)
const upserted = await mcp_upsert_document({
  connection_id: "development",
  container_id: "users",
  document: {
    id: "user-789",
    email: "[email protected]",
    name: "Jane Doe"
  },
  partition_key: "user-789"
});

// Delete a document
const deleted = await mcp_delete_document({
  connection_id: "development",
  container_id: "users",
  document_id: "user-456",
  partition_key: "user-456"
});

🔧 Connection File Schema

interface ConnectionConfig {
  id: string;                    // Unique identifier for the connection
  connectionString: string;      // CosmosDB connection string
  databaseId: string;            // Database ID to connect to
  allowModifications?: boolean;  // Enable write operations (default: false)
  description?: string;          // Optional description
}

Example cosmos-connections.json:

[
  {
    "id": "athlete",
    "connectionString": "AccountEndpoint=https://dbsqlcosmosathlete.documents.azure.com:443/;AccountKey=...;",
    "databaseId": "data",
    "allowModifications": false,
    "description": "Athlete data"
  },
  {
    "id": "events",
    "connectionString": "AccountEndpoint=https://dbsqlcosmosevents.documents.azure.com:443/;AccountKey=...;",
    "databaseId": "events",
    "allowModifications": false,
    "description": "Events data"
  }
]

🚨 Troubleshooting

Connection Issues:

  • Invalid connection string: Verify connection string format includes AccountEndpoint and AccountKey
  • Database not found: Check databaseId matches existing database
  • Request timeout: Increase COSMOS_MAX_RETRY_WAIT_TIME or check network

Query Issues:

  • Query timeout: Use TOP N to limit results, specify only needed fields, avoid SELECT *
  • Cross partition query required: Set enable_cross_partition: true in query parameters
  • Partition key required: Specify partition_key for single-partition operations

Multi-Connection Issues:

  • Connection not found: Use mcp_list_connections to see available connection IDs
  • Wrong database: Verify the connection_id parameter points to the correct connection

Write Operation Blocked:

  • Error: "Database modifications are disabled": Set allowModifications: true in connection config or DB_ALLOW_MODIFICATIONS=true
  • This is a safety feature - write operations are disabled by default

CosmosDB Emulator:

  1. Install Azure CosmosDB Emulator
  2. Start emulator on port 8081
  3. Use default emulator connection string
  4. Create database and containers for testing

🧪 Development

npm test          # Run tests
npm run build     # Build project
npm start         # Development mode

🏗️ Architecture

Project Structure:

src/
├── tools/                    # Tool implementations
│   ├── containerAnalysis.ts  # Container operations
│   ├── dataOperations.ts     # Data queries & CRUD
│   └── types.ts              # Type definitions
├── db.ts                     # CosmosDB connection & multi-connection management
├── server.ts                 # MCP server setup
└── tools.ts                  # Tool definitions

Key Features:

  • ⚡ Connection caching and pooling
  • 🔗 Multi-connection management
  • 🛡️ Comprehensive error handling
  • 🔒 Write operation protection per connection
  • 📊 Performance metrics and request charges
  • 🔧 Flexible configuration options
  • 📋 Intelligent schema analysis

📝 Important Notes

  • Query Best Practices: Always use TOP N and specify fields - never use SELECT *
  • Container IDs: Use exact names as in CosmosDB
  • Partition Keys: Required for optimal performance and CRUD operations
  • Cross-Partition Queries: Can be expensive; use filters
  • Request Charges: Monitor RU consumption
  • Security: Store connection strings securely (use external file)
  • Write Protection: Enable only for connections that need it

🤝 Contributing

  1. Fork the repository
  2. Create feature branch (git checkout -b feature/name)
  3. Make changes and add tests
  4. Ensure tests pass (npm test)
  5. Commit changes (git commit -m 'Add feature')
  6. Push and open Pull Request

📄 License

MIT License - see LICENSE file for details.

🏷️ Tags & Keywords

Database: cosmosdb azure-cosmosdb nosql document-database database-analysis database-tools azure database-management database-operations data-analysis multi-database

MCP & AI: model-context-protocol mcp-server mcp-tools ai-tools claude-desktop cursor-ide anthropic llm-integration ai-database intelligent-database

Technology: typescript nodejs npm-package cli-tool database-client nosql-client database-sdk rest-api json-api database-connector

Features: container-analysis document-operations sql-queries schema-analysis query-execution database-search data-exploration database-insights partition-management throughput-analysis crud-operations document-crud multi-connection

Use Cases: database-development data-science business-intelligence database-migration schema-documentation performance-analysis data-governance database-monitoring troubleshooting automation

🙏 Acknowledgments

🎯 MCP CosmosDB provides comprehensive Azure CosmosDB database analysis through the Model Context Protocol. Perfect for developers and data analysts working with CosmosDB! 🚀

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.