CockroachDB MCP

CockroachDB MCP exposes a CockroachDB cluster to an AI agent over the Model Context Protocol, turning schema inspection, query execution and cluster diagnostics into tools an assistant can call. It exists both as a managed endpoint inside CockroachDB Cloud and as self hosted implementations that connect to a cluster with a standard connection string. The server covers three surfaces. For schema, an agent can list databases and tables and describe columns, constraints and indexes, which gives it the structure it needs before writing SQL. For data, it runs read only SQL and returns results, and produces EXPLAIN output so a query plan can be read rather than guessed. For operations, it reports cluster and node health, replication state, running and slow queries, contention hotspots and index recommendations. Write operations such as creating a database or table and inserting rows sit behind an explicit opt in, with read only as the default posture. It suits backend and platform engineers who want a coding assistant to answer questions about a live schema, sanity check a query plan, or explain why a statement is slow, without granting a model open ended write access to production data. The read only default is the part worth verifying at setup, since the same interface becomes a mutation path the moment writes are enabled.