Get the names of all the accessible buckets in the cluster.

Get the server status and configuration without establishing connection. This tool can be used to verify if the server is running and check the configuration.

Test the connection to Couchbase cluster and optionally to a bucket. This tool verifies the connection to the Couchbase cluster and bucket by establishing the connection if it is not already established. If bucket name is not provided, it will not try to connect to the bucket specified in the MCP server settings. Returns connection status and basic cluster information.

Get the names of all scopes and collections in the bucket. Returns a dictionary with scope names as keys and lists of collection names as values.

Get the names of all collections in the given scope and bucket.

Get the names of all scopes in the given bucket.

Get cluster health status and list of all running services.

This tool provides health monitoring by:

• Getting health status of all running services with latency information (via ping)

• Listing all services running on the cluster with their endpoints

• Showing connection status and node information for each service

If bucket_name is provided, it actively pings services from the perspective of the bucket. Otherwise, it uses cluster-level ping to get the health status of the cluster.

Returns:

• Cluster health status with service-level connection details and latency measurements

Get a document by its ID from the specified scope and collection. If the document is not found, it will raise an exception.

Get the schema for a collection in the specified scope. Returns a dictionary with the collection name and the schema returned by running INFER query on the Couchbase collection.

Run a SQL++ query on a scope and return the results as a list of JSON objects.

The query will be run on the specified scope in the specified bucket. The query should use collection names directly without bucket/scope prefixes, as the scope context is automatically set.

Example: query = "SELECT * FROM users WHERE age > 18" # Incorrect: "SELECT * FROM bucket.scope.users WHERE age > 18"

Generate and evaluate an EXPLAIN plan for a SQL++ query. It provides information about the execution plan for the query.

The EXPLAIN statement is run in the specified scope in the specified bucket. It returns query metadata along with an extracted plan and plan evaluation.

Get index recommendations from Couchbase Index Advisor for a given SQL++ query.

The Index Advisor analyzes the query and provides recommendations for optimal indexes. This tool works with SELECT, UPDATE, DELETE, or MERGE queries. The queries will be run on the specified scope in the specified bucket.

Returns a dictionary with:

• current_used_indexes: Array of currently used indexes (if any)

• recommended_indexes: Array of recommended secondary indexes (if any)

• recommended_covering_indexes: Array of recommended covering indexes (if any)

Each index object contains:

• index: The CREATE INDEX SQL++ command

• statements: Array of statement objects with the query and run count

List indexes in the cluster with optional filtering by bucket, scope, collection, and index name.

Filters must be provided hierarchically: scope requires bucket, collection requires both, index requires all three. Set return_raw_index_stats=True to get the unprocessed source row for each index.

Each result contains: name, definition (CREATE INDEX statement), status, isPrimary, bucket, scope, collection, lastScanTime. If a required field is missing, the entry contains warning and raw_index_stats instead.

Source depends on cluster version: v8+ queries system:indexes via the query service (RBAC-scoped — the connected user sees only indexes on keyspaces they can access); older clusters fall back to the admin-level Index Service REST API /getIndexStatus.

Get queries that are not very selective from the system:completed_requests catalog.

Get queries that don't use a covering index from the system:completed_requests catalog.

Get queries that use a primary index from the system:completed_requests catalog.

Get queries with the largest result counts from the system:completed_requests catalog.

Get queries with the largest response sizes from the system:completed_requests catalog.

Get the N longest running queries from the system:completed_requests catalog.

Get the N most frequent queries from the system:completed_requests catalog.