dhi.io/couchbase-mcp
Couchbase MCP Server
The official Couchbase MCP server that connects AI tools and assistants to Couchbase clusters — running SQL++ queries, browsing buckets, scopes, and collections, performing key-value operations, and checking cluster health — over stdio transport, read-only by default.
pushed 15 hours ago
linux/amd64, linux/arm64
50.14 MB
for linux/amd64
187
for linux/amd64
Active support
-
Build Level 3
Tamper-evident proof of how and from what sources this image was built. Build Level 3 is the highest the SLSA build track defines.
CycloneDX SBOM + SPDX SBOM
A software bill of materials in both CycloneDX and SPDX formats so it drops straight into your existing tooling. Audit exactly what you're shipping.
A Vulnerability Exploitability exchange document, Docker's assessment of which CVEs actually affect this image and which don't apply, so you can focus on real risk instead of chasing false positives.
Available
A link to everything used to build the image, package source code, Git repos, and build files, so you can audit or reproduce the build and stay compliant with open source licenses.
Every known vulnerability in this image, shown in full rather than hidden. The VEX data flags which ones actually apply, so you can tell real exposure from noise before you ship.
Exactly what changed in this build, down to the package bumps and fixes behind the version you're pulling.
Verifies no keys, tokens, or credentials were accidentally baked into the image.
The image layers were scanned for known malware signatures before publishing.
About Couchbase MCP Server
The Couchbase MCP Server is the official Model Context Protocol implementation for Couchbase, maintained by Couchbase's Developer Experience & Ecosystem team. It connects AI tools and assistants to Couchbase clusters, letting agents run SQL++ queries, browse buckets, scopes, and collections, perform key-value operations, inspect schema, and check cluster health through natural language interactions.
The server communicates over stdio transport (the default mode used by desktop MCP clients) and is launched as a
one-shot container; it can also run in HTTP or SSE mode for remote clients. It is read-only by default — all write
operations are disabled unless explicitly enabled — and supports both username/password and mutual-TLS authentication.
Connection details are supplied through the CB_CONNECTION_STRING, CB_USERNAME, and CB_PASSWORD environment
variables. The RBAC permissions granted to the Couchbase user remain the primary security control; the server's
read-only mode and tool-disabling options provide additional layers.
For more details, visit https://mcp-server.couchbase.com/.
About Docker Hardened Images
Docker Hardened Images are built to meet the highest security and compliance standards. They provide a trusted foundation for containerized workloads by incorporating security best practices from the start.
Why use Docker Hardened Images?
These images are published with near-zero known CVEs, include signed provenance, and come with a complete Software Bill of Materials (SBOM) and VEX metadata. They're designed to secure your software supply chain while fitting seamlessly into existing Docker workflows.
Trademarks
Couchbase® is a registered trademark of Couchbase, Inc. All rights in the mark are reserved to Couchbase, Inc. Any use by Docker is for referential purposes only and does not indicate sponsorship, endorsement, or affiliation.