M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionCouchbase MCP ServerLet AI agents securely connect to and work with data in Couchbase clustersDBHubBytebase's official, minimalist two-tool database MCP server
FMRS72 / 100 · B74 / 100 · B
Reliability11 / 2013 / 20
Security and permissions16 / 2013 / 20
Maintenance13 / 2016 / 20
Documentation18 / 2015 / 20
Setup experience14 / 2017 / 20
Best for
  • Developers and data teams who want safe AI access to Couchbase data in mainstream MCP clients (Claude Desktop, Cursor, Windsurf, VS Code, JetBrains IDEs)
  • Teams already using Couchbase (Capella or self-managed) who want LLM-assisted querying and analysis
  • Scenarios wanting the smallest possible tool count and lowest context-window overhead for database access
  • Cases needing to grant non-technical teammates safe, read-only database access
Not for
  • Unattended write access to production databases without risk assessment (read-only mode blocks writes by default)
  • Users not running Couchbase or without a running cluster
  • Those needing official support-portal assistance (community-maintained; GitHub only)
  • Scenarios needing database administration operations (creating indexes, altering schema) rather than just querying (DBHub is positioned as a query tool, not a DBA management tool)
Required permissions
  • Couchbase connection string plus username/password for basic auth, or client certificate and key paths for mTLS, via environment variables or CLI arguments
  • CA root certificate path for TLS with self-signed/untrusted certificates on non-Capella clusters
  • Database user needs RBAC permissions to access at least one bucket — RBAC is the authoritative security control
  • Requires a database connection string (DSN), which may contain sensitive credentials
  • execute_sql can run arbitrary SQL (including writes) by default — must be constrained via read-only mode or the underlying database account's own permissions
Risks and side effects
  • CB_MCP_READ_ONLY_MODE defaults to true, disabling all writes; when false, the LLM can modify/delete documents, scopes, collections, and indexes
  • Disabling tools alone is not sufficient: SQL++ DML can still modify data via run_sql_plus_plus_query; use read-only mode or proper RBAC
  • delete_scope/delete_collection permanently destroy data
  • The HTTP endpoint is unauthenticated unless OAuth is configured
  • LLM outputs may be inaccurate; Couchbase does not review them and users are solely responsible
  • The product automatically collects usage/performance data (e.g., product version, IP address); see the Couchbase Privacy Policy
  • Under default settings, if the connected database account has write access, execute_sql could let the assistant perform an unintended write or delete — pair with a read-only database account in production
  • The DSN contains a plaintext password — pay attention to the access permissions on wherever the config is stored
Supported clientsClaude Desktop, Cursor, Windsurf Editor, VS Code, JetBrains IDEsClaude Desktop, Claude Code, VS Code, Cursor, Zed
Tools332