CockroachDB Cloud MCP server

What the model can do

CockroachDB Cloud: clusters with plan, state, version, regions, node counts, hardware or usage limits and delete protection, one cluster's backup settings and maintenance window, databases, nodes and their status, backups and restore jobs, the IP allowlist, folders, and the organisation's audit log; when you ask, can create, rename or delete a database, add or remove an allowlist entry, set the maintenance window, add a blackout window, change backup settings, restore from a backup, create a folder, turn delete protection on or off, change node counts, upgrade the CockroachDB version and delete a cluster.

Reads

• cockroachcloud_clustersClusters in the organisation: name, plan (Basic, Standard, Advanced), state, any running operation, upgrade status and version…
• cockroachcloud_clusterOne cluster by id, with its backup settings (enabled, frequency, retention) and, for Advanced clusters, its weekly maintenance window.
• cockroachcloud_databasesDatabases on a cluster, by name, with their table counts.
• cockroachcloud_nodesNodes of a cluster with their region and status (LIVE or NOT_READY), and a count of nodes not ready.
• cockroachcloud_backupsA cluster's managed backups (id and the point in time each restores to) and its restore jobs (type, status, progress, source and destination…
• cockroachcloud_allowlistA cluster's IP allowlist: each CIDR range with its name and whether it may reach SQL and/or the DB Console, and whether a change is still propagating.
• cockroachcloud_foldersFolders that organise clusters: name, id, parent and path.
• cockroachcloud_audit_logThe organisation's audit log, newest first by default: what was done (create or delete a cluster, change the allowlist, invite a user …)…

Acts, when you ask

These change something in CockroachDB Cloud. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• cockroachcloud_create_databaseCreates an empty database on a CockroachDB Cloud cluster.
• cockroachcloud_rename_databaseRenames a database on a CockroachDB Cloud cluster; applications connecting by the old name stop finding it.
• cockroachcloud_delete_databasePermanently deletes a database and every table and row in it from a CockroachDB Cloud cluster.
• cockroachcloud_add_allowlist_entryAllows a CIDR range of IP addresses to connect to a CockroachDB Cloud cluster's SQL interface and/or DB Console, which widens who can reach it…
• cockroachcloud_remove_allowlist_entryRemoves a CIDR range from a CockroachDB Cloud cluster's IP allowlist; clients connecting from it are cut off.
• cockroachcloud_set_maintenance_windowSets an Advanced cluster's weekly maintenance window, when CockroachDB Cloud may apply patches and restart nodes: it starts offset_hours after Monday…
• cockroachcloud_create_blackout_windowAdds a blackout window to an Advanced cluster, during which no maintenance runs.
• cockroachcloud_update_backup_configChanges a cluster's managed backup settings: turn backups on or off, how often they run (minutes) and how long they are kept (2, 7, 30…
• cockroachcloud_restoreStarts a restore job into the destination cluster from a managed backup…
• cockroachcloud_create_folderCreates a folder for organising clusters, at the root or inside parent_id.
• cockroachcloud_set_delete_protectionTurns a cluster's delete protection on or off.
• cockroachcloud_scale_nodesSets the number of nodes in one or more regions of an Advanced cluster (region code as the cloud names it, e.g. us-west2 on GCP, us-west-2 on AWS).
• cockroachcloud_upgrade_versionStarts a CockroachDB major-version upgrade of a cluster (when its upgrade status is UPGRADE_AVAILABLE) by naming the target version, e.g. v24.2…
• cockroachcloud_delete_clusterPermanently deletes a CockroachDB Cloud cluster and all of its data; billing for it stops.

Connect it

First connect CockroachDB Cloud on Dashboard → Connections, then add Memtro to your client once. The CockroachDB Cloud tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared CockroachDB Cloud connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which CockroachDB clusters have an upgrade available?
• › Are any nodes not ready on the prod cluster?
• › How long are backups kept on the orders cluster?
• › Which IP ranges can reach the analytics cluster's SQL interface?
• › Did last night's restore job finish?

Questions

Is this an official CockroachDB Cloud MCP server?

No. It is Memtro's MCP server with Memtro's CockroachDB Cloud connector behind it: the connector reads CockroachDB Cloud through its API with the credentials you connect on Dashboard → Connections, and CockroachDB Cloud publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in CockroachDB Cloud?

Only when you ask, and only what it has been granted: create a database; rename a database; delete a database; add an IP allowlist entry; remove an IP allowlist entry; set a cluster's weekly maintenance window; add a maintenance blackout window; change a cluster's backup settings; restore a cluster, database or table from a backup; create a folder; turn a cluster's delete protection on or off; change the node count of an Advanced cluster's regions; upgrade (or roll back) a cluster's CockroachDB version; delete a cluster. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Databases and warehouses

• Postgres MCP server
• MySQL and MariaDB MCP server
• SQL Server MCP server
• BigQuery MCP server
• Snowflake MCP server
• AWS Athena MCP server