Which CockroachDB clusters need an upgrade, and are their backups running?
CockroachDB Cloud runs your managed databases. Memtro reads clusters with plan, state, version, regions, node counts, 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 audit log. When asked and granted, it can create, rename or delete a database, change the allowlist, maintenance, blackout and backup settings, restore from a backup, toggle delete protection, scale nodes, upgrade a version and delete a cluster. The audit log needs the Auditor or Org Admin role on the service account.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right CockroachDB Cloud tool, reads what it needs, and answers with the source cited.
These tools change something in CockroachDB Cloud. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once CockroachDB Cloud is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
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?
Dan Fletcher, a database engineer at Northwind, asked whether the orders cluster was backing up and how long backups were kept. Memtro read the cluster's backup settings and recent backups, and gave him the frequency, retention and latest restore point.
Priya Sharma, a platform lead at Acme Ltd, asked Memtro to let the new office's IP range reach the analytics cluster's SQL interface. Memtro added the allowlist entry, then read the allowlist back to show the new range and whether the change had propagated.
The teams that lean on CockroachDB Cloud most, a question each of them asks, and what they connect beside it.
A record in CockroachDB Cloud is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Grist
NocoDB
Typesense
Weaviate
Tinybird
Hightouch
Census
kintone
Monte Carlo
OpenMetadata
Secoda
Softr
Teable
VectaraIn CockroachDB Cloud, open Access Management → Service Accounts and give a service account Cluster Operator or Cluster Admin, plus Auditor for the audit log. Create API Key and copy the secret key, which is shown once.
In Memtro, open Connections → CockroachDB Cloud and paste the Service account secret key.
An administrator grants the database, allowlist, backup and cluster actions by name to the teams that may use them, keeping cluster deletion to the people who need it.
Ask which CockroachDB clusters have an upgrade available.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The CockroachDB Cloud tools are the same everywhere.
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. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded. An hourly sync anchors recently changed CockroachDB Cloud records into memory as entities.
Service account secret key. In CockroachDB Cloud, open Access Management → Service Accounts and give a service account Cluster Operator or Cluster Admin, plus Auditor for the audit log. Create API Key and copy the secret key, which is shown once.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
