Couchbase MCP Server
Related Servers
Alternatives to Couchbase MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables large language models to interact directly with Couchbase databases through natural language, supporting operations like querying buckets, performing CRUD operations, and executing N1QL queries.5 npm7MIT
- AlicenseNot gradedqualityDmaintenanceA server that enables natural language interactions with Couchbase databases through the Model Context Protocol, allowing users to perform SQL++ queries on Couchbase Capella clusters using conversational commands.1MIT

YugabyteDB MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceAn MCP server implementation that allows Large Language Models to directly interact with YugabyteDB databases, supporting table listing and read-only SQL queries.10Apache 2.0- AlicenseNot gradedqualityDmaintenanceEnables LLMs to interact directly with Couchbase databases, supporting CRUD operations, N1QL queries, and data management through natural language.5 npmMIT
- AlicenseAqualityCmaintenanceEnables natural-language AI agents to query and manage Couchbase databases via the Model Context Protocol, allowing users to ask plain-English questions about travel data and get SQL++-backed answers.5MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables large language models to interact directly with MongoDB databases, allowing them to query collections, inspect schemas, and manage data through natural language.19 npmMIT
TDQS
Scored across 22 tools
Tools are mostly distinct: schema, document CRUD, query execution, and query analysis are clearly separated. A few overlaps exist: get_cluster_health_and_services vs get_cluster_diagnostics_report both check connectivity but explicitly differentiate active vs passive checks, and the get_queries_* tools are all similar but each targets a specific metric (selectivity, covering index, primary index, result count, etc.). Still, the descriptions are thorough enough to guide selection.
Most tools follow a verb_noun pattern: get_schema_for_collection, get_document_by_id, lookup_subdocument, run_sql_plus_plus_query, test_cluster_connection. However, there are deviations: get_queries_not_selective and get_longest_running_queries are more adjective-based, and 'lookup_subdocument' uses 'lookup' instead of 'get'. Despite mixed verb choices (get, lookup, run, test), the pattern is clear and predictable.
With 22 tools, the server is on the higher end but still well-scoped for a comprehensive Couchbase interaction layer covering schema, documents, querying, cluster health, and query analysis. The count is justified by the breadth of features (e.g., 7 query-analysis tools). It feels slightly heavy but not excessive.
The server provides read operations for documents (get, lookup subdocument) but lacks create, update, and delete for documents. It also lacks bucket/scope/collection management (create/drop). Query analysis is thorough with index advisor and health metrics. The gap in write operations is notable and will force agents to rely on raw SQL++ for mutations, which is a significant omission.