Can I use CockroachDB as a CLI?

Yes. KosmoKrator exposes a CockroachDB CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose CockroachDB through MCP?

Yes. The KosmoKrator MCP gateway can expose selected CockroachDB tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are CockroachDB credentials stored?

CockroachDB credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for CockroachDB MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

data

CockroachDB MCP Integration for Codex

Connect CockroachDB to Codex through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 6 read 1 write Bearer token auth

Submit CockroachDB feedback View package source

Connect CockroachDB to Codex

Use KosmoKrator as a local MCP proxy for Codex so coding sessions can reach selected integrations with explicit write policy.

Register kosmo mcp:serve as a local stdio server and choose the integration allowlist. The gateway is local, scoped to this integration, and starts with --write=deny so Codex can inspect read-capable tools without receiving write access by default.

CockroachDB MCP Config for Codex

Keep write access denied or ask-based unless the workspace is trusted.

{
  "mcpServers": {
    "kosmokrator-cockroachdb": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=cockroachdb",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=cockroachdb --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only CockroachDB instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

CockroachDB Tools Visible to Codex

Codex sees stable MCP tool names generated from the CockroachDB integration catalog.

MCP tool	Source function	Type	Description
`integration__cockroachdb__cockroachdb_list_clusters`	`cockroachdb.cockroachdb_list_clusters`	Read	List all CockroachDB clusters in the organization. Returns cluster IDs, names, status, cloud provider, and regions.
`integration__cockroachdb__cockroachdb_get_cluster`	`cockroachdb.cockroachdb_get_cluster`	Read	Get details for a specific CockroachDB cluster by ID. Returns full cluster information including configuration, nodes, and connection strings.
`integration__cockroachdb__cockroachdb_create_cluster`	`cockroachdb.cockroachdb_create_cluster`	Write	Create a new CockroachDB cluster. Requires a name, cloud provider, and region configuration.
`integration__cockroachdb__cockroachdb_list_databases`	`cockroachdb.cockroachdb_list_databases`	Read	List all databases in a CockroachDB cluster. Returns database names, sizes, and table counts.
`integration__cockroachdb__cockroachdb_get_database`	`cockroachdb.cockroachdb_get_database`	Read	Get details for a specific database in a CockroachDB cluster. Returns table list, sizes, and configuration.
`integration__cockroachdb__cockroachdb_list_users`	`cockroachdb.cockroachdb_list_users`	Read	List all SQL users in a CockroachDB cluster. Returns usernames and privileges.
`integration__cockroachdb__cockroachdb_get_current_user`	`cockroachdb.cockroachdb_get_current_user`	Read	Get information about the current authenticated CockroachDB Cloud user, including email, name, and organization role.

Related CockroachDB Pages

CockroachDB CLIUse direct JSON commands instead of MCP discovery. CockroachDB MCPFull gateway reference and MCP tool names. KosmoKrator for CodexClient-level gateway setup.