Field-by-field comparison
Compare the evidence before choosing an MCP.
Each signal stays separate, missing facts remain visible, and the column order follows your selection.
| Evidence field | Couchbase MCPShortlist candidate | Google MCP Toolbox for DatabasesMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP Couchbase · Publisher source ↗ | First-party MCP Google · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Not documented Package: Not documented | Repo: Sep 24, 2026 Package: Not documented |
| Popularity evidence | ||
| GitHub stars | 34 GitHub stars · checked 2026-10-20 | 16,485 GitHub stars · checked 2026-09-24T04:14:16.258000Z |
| Package downloads / 30 days | 1,200 package downloads / 30 days · checked 2026-10-20 | No reliable download data |
| Client coverage | ||
| Client coverage details | Not documented | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | For stdio/local use, Couchbase supports username/password or mTLS to the cluster. For Streamable HTTP, the MCP server can additionally act as an OAuth 2.1 resource server validating bearer JWTs. | Authentication depends on the database source and can include database username/password, Google Cloud IAM, or other source-specific mechanisms. Use a dedicated read-only identity and secret manager or protected environment variables. |
| Cost | The MCP package is open source. Running it requires a Couchbase cluster; Capella and enterprise offerings can be paid, and enterprise support for the MCP server is tied to Couchbase AI Data Plane licensing. | The Apache-licensed Toolbox and npm server have no documented MCP usage fee. Database services, Google Cloud resources, network transfer, observability backends, hosting, and the AI client may incur normal charges. |
| Permissions | Couchbase RBAC is the authoritative security boundary. The server is read-only by default; write tools are not loaded unless read-only mode is disabled. HTTP OAuth can separately gate read and write scopes. | Effective permissions come from each configured database identity and the enabled prebuilt or custom tools. Generic prebuilt sets can include schema discovery and execute_sql; custom tools can constrain statements, parameters, and accessible sources. |
| Data handling | Couchbase says the MCP product collects usage/performance data such as product/version and browser information such as IP address, but does not access or collect the data stored in Couchbase products. Local logs can include lifecycle/tool invocation information depending on configured log level. | The Toolbox process connects directly to configured databases and returns selected schemas, rows, query results, and errors to the MCP client. Credentials may be supplied through environment variables or configuration; integrated cloud authentication and OpenTelemetry are available. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | If read-only mode is disabled, the MCP can modify documents, collections, indexes and other database state. Remote HTTP without OAuth is unauthenticated, so exposing it that way is unsafe. | Generic SQL tools can expose or mutate large amounts of data and retrieved database text can carry prompt-injection content. Prefer a non-production replica, read-only credentials, allow-listed custom parameterized tools, query limits, audit logs, and no secrets in config. This review does not claim MCP100 execution testing. |
| Evidence date | ||
| Editorial review | 2026-10-19 | 2026-07-24 |
| Candidate evidence | 2026-10-19 | 2026-09-24T04:25:05.554391Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →