MCP server for Azure Cosmos DB using the Go SDK

What is MCP server for Azure Cosmos DB using the Go SDK?

This is an experimental MCP server built with Go that exposes tools to interact with Azure Cosmos DB using the Azure SDK for Go and the official MCP Go SDK. It works with the Azure Cosmos DB service and the vNext emulator, and is intended as a learning tool rather than a production replacement for other Azure MCP offerings.

How to use MCP server for Azure Cosmos DB using the Go SDK?

Clone the repository, build the binary with go build, then run in HTTP or stdio mode. Authentication uses Azure’s DefaultAzureCredential (except for the local emulator, which uses key-based auth). Configure the server in your MCP client via a mcp.json file, setting either an HTTP URL or a stdio command.

Key features of MCP server for Azure Cosmos DB using the Go SDK

• List, create, and manage databases and containers.
• Add and read items in containers.
• Execute SQL queries with optional partition key scoping.
• Batch-create items using transactional batch operations.
• Supports Streamable HTTP and stdio transports.
• Can run locally or be deployed to a remote endpoint.

Use cases of MCP server for Azure Cosmos DB using the Go SDK

• Allow an AI assistant to list databases and containers in a Cosmos DB account.
• Create a new container with a defined partition key via a chat tool.
• Read specific items or execute SQL queries across containers.
• Learn how to combine the Azure Go SDK and MCP Go SDK for building AI tooling.

FAQ from MCP server for Azure Cosmos DB using the Go SDK

How does the server authenticate with Azure Cosmos DB?

It uses DefaultAzureCredential from the Azure SDK for Go, supporting environment variables, managed identity, Azure CLI, and Azure Developer CLI. The local emulator uses a well-known key-based authentication instead.

What transports are supported?

The server supports both Streamable HTTP and Stdio transports. You can run locally as an HTTP server or stdio process, or deploy to a remote endpoint as an HTTP(s) server.

Is this server production-ready?

No. This project is an experimental learning tool and is not intended to replace the Azure MCP Server or Azure Cosmos DB MCP Toolkit. The remote execution mode lacks client authentication, so use it only for testing.

What tools are exposed?

It exposes nine tools: List Databases, Create Database, List Containers, Read Container Metadata, Create Container, Add Item to Container, Read Item, Execute Query, and Batch Create Items.

Can I use the local Cosmos DB emulator?

Yes. Set up the vNext emulator with docker run ..., then configure the server—it will work with both local and cloud accounts.