Couchbase MCP Server

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"

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

Args:
    ctx: MCP context for cluster connection
    bucket_name: Optional bucket name to filter indexes
    scope_name: Optional scope name to filter indexes (requires bucket_name)
    collection_name: Optional collection name to filter indexes (requires bucket_name and scope_name)
    index_name: Optional index name to filter indexes (requires bucket_name, scope_name, and collection_name)
    include_raw_index_stats: If True, include raw index stats (as-is from API) in addition
                          to cleaned-up version. Default is False.

Returns:
    List of dictionaries with keys:
    - name (str): Index name
    - definition (str): Cleaned-up CREATE INDEX statement
    - status (str): Current status of the index (e.g., "Ready", "Building", "Deferred")
    - isPrimary (bool): Whether this is a primary index
    - bucket (str): Bucket name where the index exists
    - scope (str): Scope name where the index exists
    - collection (str): Collection name where the index exists
    - raw_index_stats (dict, optional): Complete raw index status object from API including metadata,
                                       state, keyspace info, etc. (only if include_raw_index_stats=True)

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

Args:
    limit: Number of queries to return (default: 10)

Returns:
    List of queries where index scans return significantly more documents than the final result

Args:
    limit: Number of queries to return (default: 10)

Returns:
    List of queries that perform index scans but also require fetches (not covering)

Args:
    limit: Number of queries to return (default: 10)

Returns:
    List of queries that use primary indexes, ordered by result count

Args:
    limit: Number of queries to return (default: 10)

Returns:
    List of queries with their average result count

Args:
    limit: Number of queries to return (default: 10)

Returns:
    List of queries with their average result size in bytes, KB, and MB

Args:
    limit: Number of queries to return (default: 10)

Returns:
    List of queries with their average service time and count

Args:
    limit: Number of queries to return (default: 10)

Returns:
    List of queries with their frequency count