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 | Supabase MCPMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP Couchbase · Publisher source ↗ | First-party MCP Supabase · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Not documented Package: Not documented | Repo: Sep 24, 2026 Package: Sep 21, 2026 |
| Popularity evidence | ||
| GitHub stars | 34 GitHub stars · checked 2026-10-20 | 2,919 GitHub stars · checked 2026-09-24T04:16:20.864000Z |
| Package downloads / 30 days | 1,200 package downloads / 30 days · checked 2026-10-20 | 406,869 package downloads / 30 days · checked 2026-09-24T04:17:50.300000Z |
| Client coverage | ||
| Client coverage details | Not documented | Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP |
| 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. | Hosted MCP uses browser OAuth and grants organization access to the MCP client. Project scope, read-only mode, and feature groups are encoded in URL query parameters. Enterprise-managed authentication is GA for eligible Team and Enterprise organizations. Access remains scoped to each user's existing Supabase role and permissions. |
| 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 MCP server is open source; normal Supabase plan, database, branch, Edge Function, storage, and usage charges apply. Branching and some storage operations require a paid plan. |
| 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. | Without project_ref the hosted server can access all projects in the authorized organization. With project_ref it is limited to one project. read_only=true uses a read-only Postgres user for SQL and disables listed mutation tools. Feature groups can further narrow exposed tools. |
| 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. | Enabled tools may return schemas, table data from executed queries, logs, security/performance advisors, project metadata, publishable keys, types, and Edge Function source. Hosted mode sends tool requests through Supabase's MCP service. |
| 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. | Unscoped or write-enabled access can affect every project in an organization, execute SQL, apply migrations, deploy functions, or manage branches. Always set project_ref and read_only=true first, minimize feature groups, and avoid production data. |
| Evidence date | ||
| Editorial review | 2026-10-19 | 2026-09-05 |
| 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 →