Tools
- reference
Reference of the tools the Couchbase MCP Server for Operational Insights exposes, grouped by category, with how the server handles large query results.
The Couchbase MCP Server for Operational Insights exposes several tools across multiple categories. The list of supported tools is constantly evolving, so see the README for the latest set of tools. Each tool is available to LLMs through the MCP protocol.
The Operational Insights server supports only self-managed deployments. For the Couchbase Server tools, see Couchbase Server Tools.
Server Status
Tool for checking server status.
It’s shared with the Couchbase Server server, so it keeps its name without an operational_insights_ prefix.
| Tool | Description |
|---|---|
|
Get the server status and configuration without connecting to the cluster. The tool reports read-only mode, the tools that are turned off or need confirmation, OAuth settings, the resolved logging configuration, and the audit logging counters. It shows the connection string and username in clear text. For the password and certificates, it shows only whether they’re set. |
Data Model & Schema Discovery
Tools for exploring databases, scopes, collections, and document schemas.
| Tool | Description |
|---|---|
|
Get a list of all the databases in the cluster. |
|
Get a list of all the scopes in the specified database. |
|
Get a list of all the collections in the specified scope, including the type of each collection: |
|
Infer the JSON schema of a collection with the |
Query and Index
Tools for running SQL++ queries, managing async queries, and working with indexes.
For how to limit or export large query results, see Large Result Handling.
Read-only mode turns off operational_insights_create_index by default.
All the other tools stay available in read-only mode, including operational_insights_cancel_async_query.
| The async query tools are stateful. The server keeps each query handle in the memory of one process, so a restart loses all handles. If you run more than one Operational Insights server behind a load balancer, route all requests for a handle to the same server. For symptoms and fixes, see Async Query Issues. |
| Tool | Description |
|---|---|
|
List the secondary indexes that users created, optionally filtered by database, scope, and collection. The tool does not list primary indexes, optimizer samples, or internal System indexes. |
|
Get the query plan for a SQL++ statement with EXPLAIN, without running it. Pass the statement without the |
|
Run a SQL++ statement and return its result rows, up to the size limit that you configure. The statement can be SELECT, DML, or DDL. To send a large result to object storage instead, use the |
|
Start a SQL++ query without waiting for it to finish. The tool returns a |
|
Check the status of an async query and get its results once it finishes. While the query runs, the tool returns |
|
Free the results of a finished async query on the server. Fetching results does not free them. If the query is still running, the tool returns |
|
Stop an async query that’s still running. The query handle stops working. If the query already finished, the tool returns |
|
Create a secondary index with |