Integrations · CockroachDB
Guild agents create and scale CockroachDB Cloud clusters, manage databases and SQL users, control network access, and trigger backups. They can also inspect schemas and run SQL through CockroachDB Cloud’s managed MCP server. Guild offers two CockroachDB integrations: one for the Cloud API, one for the MCP server. Both keep your credential server-side, and credential policies decide which operations each agent may call.
Book a demo
See how teams govern agents that use CockroachDB.
Talk to sales
Get access to Guild, then connect CockroachDB to your first agent.
Choose an integration
Both integrations reach CockroachDB Cloud. They differ in what they cover.
Use CockroachDB when an agent administers clusters: provisioning, scaling, users, network access, or backups. Use CockroachDB MCP for an agent that reads or writes data, so it gets a typed tool for each SQL operation instead of a raw JSON-RPC passthrough.
How it works
1
Create a CockroachDB Cloud service account
In the CockroachDB Cloud Console, create a service account with an API key. Give it only the roles your agent needs. Each tool lists the roles it requires.
2
Connect the credential in Guild
Go to Access & setup > Credentials, click Connect, select cockroachdb or cockroachdb-mcp, and paste the key into API Key.
3
Import tools and pick what you need
Import the integration’s tools and use
pick() to include only the tools your agent needs.Why CockroachDB access needs governing
CockroachDB tools can delete clusters and all their data, drop databases, remove SQL users, modify IP allowlists, and write rows. Guild’s credential proxy enforces credential policies before any request leaves the platform. You can write ALLOW and DENY rules that restrict which operations an agent may call, scope rules to specific agents or workspaces, and use wildcard patterns such as*_delete to block entire classes of destructive operations. The API key is injected server-side only after the policy check passes, so agents never handle the secret directly.
Guild logs every credential proxy call, giving you a record of which agent called which CockroachDB operation and when. You can tighten rules incrementally: start with the default allow-all policy while building, then delete it once your scoped rules cover everything agents should reach. At that point, any unmatched request is denied by default rather than passed through.
The service account’s CockroachDB roles are a second limit. A key without write access can’t run the MCP server’s write tools, whatever your Guild policies allow.
Authentication
- Type: API key from a CockroachDB Cloud service account
- Header: Guild sends the key as a bearer token in the
Authorizationheader - Applies to: both integrations
Usage
CockroachDB
CockroachDB MCP
Tools
CockroachDB tools
Tools in the latest published version ofguildlabs~cockroachdb:
All 39 tools
All 39 tools
CockroachDB MCP tools
Tools in the latest published version ofguildlabs~cockroachdb-mcp:
Frequently asked questions
Which integration should an agent use to run SQL?
Which integration should an agent use to run SQL?
CockroachDB MCP. It calls CockroachDB Cloud’s managed MCP server directly. The CockroachDB integration can reach the same server through
cockroachdb_mcp_call, but the agent has to build each JSON-RPC request and parse the event-stream response itself.Can an agent write data?
Can an agent write data?
Yes, if the service account has write access. The MCP server can create databases and tables and insert rows. It doesn’t run
DROP or TRUNCATE, and it blocks system schemas. Each call runs one statement, with a 20-second timeout and a 10 KiB response cap.Can I connect both CockroachDB integrations at once?
Can I connect both CockroachDB integrations at once?
Yes. Each integration has its own credential, and you can paste the same service account key into both.
How do I stop an agent from deleting clusters?
How do I stop an agent from deleting clusters?
Add a DENY rule in credential policies targeting the
cockroachdb_delete_cluster operation, or use the wildcard pattern *_delete to block all delete-style operations. The credential proxy enforces the rule before the request reaches CockroachDB.Can I give one agent a different CockroachDB key than the rest of my workspace?
Can I give one agent a different CockroachDB key than the rest of my workspace?
Yes. Connect a dedicated credential from the installed agent’s detail page. Guild resolves that credential first for that agent and never uses it for other agents or workspaces. See Credentials for the full resolution order.
Does this integration receive webhook events from CockroachDB?
Does this integration receive webhook events from CockroachDB?
No. Neither integration defines webhook events, so CockroachDB events can’t trigger agents through Guild.
Put a governed agent on CockroachDB Cloud this week
Book a demo
See how teams govern agents that use CockroachDB.
Talk to sales
Get access to Guild, then connect CockroachDB to your first agent.