Interact with the data stored in Couchbase clusters using natural language.
Couchbase MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Interact with the data stored in Couchbase clusters using natural language.
Couchbase MCP Server is a self-hosted MCP Server that allows AI agents to connect to and interact with data in Couchbase clusters, whether hosted on Capella or self-managed. It provides tools across categories including Cluster Health, Data Schema, Key-Value, Query, and Performance — with safety controls via read-only mode and fine-grained tool disabling. It supports both STDIO and Streamable HTTP transports.
Once Couchbase is connected, these are the calls the assistant has available:
get_server_configuration_status — Get the server status and configuration without connecting to the cluster — reports read-only mode, disabled/confirmation-required tools, OAuthtest_cluster_connection — Check the cluster credentials by connecting to the clusterget_cluster_health_and_services — Get cluster health status and list of all running servicesget_buckets_in_cluster — Get a list of all the buckets in the clusterget_scopes_in_bucket — Get a list of all the scopes in the specified bucketget_collections_in_scope — Get a list of all the collections in a specified scope and bucket. Note that this tool requires the cluster to have Query serviceget_scopes_and_collections_in_bucket — Get a list of all the scopes and collections in the specified bucketget_schema_for_collection — Get the structure for a collectionget_document_by_id — Get a document by ID from a specified scope and collectionupsert_document_by_id — Upsert a document by ID to a specified scope and collection. Disabled by default when CB_MCP_READ_ONLY_MODE=true.insert_document_by_id — Insert a new document by ID (fails if document exists). Disabled by default when CB_MCP_READ_ONLY_MODE=true.replace_document_by_id — Replace an existing document by ID (fails if document doesn't exist). Disabled by default when CB_MCP_READ_ONLY_MODE=true.Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 8 environment variables: CB_CONNECTION_STRING, CB_USERNAME, CB_PASSWORD, CB_CLIENT_CERT_PATH, CB_CLIENT_KEY_PATH, CB_MCP_DISABLED_TOOLS, CB_CA_CERT_PATH, CB_MCP_HOST. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Couchbase's toolset — get_server_configuration_status, test_cluster_connection, get_cluster_health_and_services and 11 more — is a fair guide to whether it matches your workflow.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| get_server_configuration_status | Get the server status and configuration without connecting to the cluster — reports read-only mode, disabled/confirmation-required tools, OAuth settings, and the resolved logging configuration |
| test_cluster_connection | Check the cluster credentials by connecting to the cluster |
| get_cluster_health_and_services | Get cluster health status and list of all running services |
| get_buckets_in_cluster | Get a list of all the buckets in the cluster |
| get_scopes_in_bucket | Get a list of all the scopes in the specified bucket |
| get_collections_in_scope | Get a list of all the collections in a specified scope and bucket. Note that this tool requires the cluster to have Query service. |
| get_scopes_and_collections_in_bucket | Get a list of all the scopes and collections in the specified bucket |
| get_schema_for_collection | Get the structure for a collection |
| get_document_by_id | Get a document by ID from a specified scope and collection |
| upsert_document_by_id | Upsert a document by ID to a specified scope and collection. **Disabled by default when CB_MCP_READ_ONLY_MODE=true.** |
| insert_document_by_id | Insert a new document by ID (fails if document exists). **Disabled by default when CB_MCP_READ_ONLY_MODE=true.** |
| replace_document_by_id | Replace an existing document by ID (fails if document doesn't exist). **Disabled by default when CB_MCP_READ_ONLY_MODE=true.** |
| delete_document_by_id | Delete a document by ID from a specified scope and collection. **Disabled by default when CB_MCP_READ_ONLY_MODE=true.** |
| list_indexes | List all indexes in the cluster with their definitions, with optional filtering by bucket, scope, collection and index name. Set return_raw_index_stats=true to return the unprocessed index information. |
{
"mcpServers": {
"couchbase": {
"command": "uvx",
"args": ["couchbase-mcp-server"],
"env": {
"CB_CONNECTION_STRING": "couchbases://connection-string",
"CB_USERNAME": "username",
"CB_PASSWORD": "password"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CB_CONNECTION_STRING | Configuration value read at startup. | Optional |
| CB_USERNAME | Configuration value read at startup. | Optional |
| CB_PASSWORD | Configuration value read at startup. | Optional |
| CB_CLIENT_CERT_PATH | Filesystem location the server is allowed to use. | Optional |
| CB_CLIENT_KEY_PATH | Credential the server authenticates with. | Yes |
| CB_MCP_DISABLED_TOOLS | Configuration value read at startup. | Optional |
| CB_CA_CERT_PATH | Filesystem location the server is allowed to use. | Optional |
| CB_MCP_HOST | Endpoint or connection string the server talks to. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.