How do I connect to a CockroachDB database?
Use the `connect_database` or `initialize_connection` tool with the JDBC URL, username, and password.
@Swayingleaves
Basic information
No overview available yet
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"cockroachdb-mcp-server-swayingleaves": {
"command": "npx",
"args": [
"-y",
"@smithery/cli",
"install",
"@Swayingleaves/cockroachdb-mcp-server",
"--client",
"claude"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
Fetch the live tool list by running this server in a temporary sandbox using the button above.
CockroachDB MCP Server is an MCP server for Cursor that allows direct interaction with a CockroachDB database. It implements the Model Context Protocol (MCP) specification, providing tools, resources, and prompts for database operations.
Install dependencies with pip install -r requirements.txt and install uv via the official install script. Configure the server in Cursor by adding a JSON entry under mcpServers with the command uv, its arguments pointing to the server directory, and the JDBC URL, username, and password. The server can then be used through Cursor's MCP integration.
Use the `connect_database` or `initialize_connection` tool with the JDBC URL, username, and password.
Check the server log file `logs/cockroachdb_mcp.log` for details. Common issues include connection refused, authentication failed, and connection timeout.
Yes, it uses psycopg2 which automatically handles special characters such as `@`, `%`, and `&` without requiring additional URL encoding.
The server enables TCP keep‑alive by default: it sends keepalive packets after 30 seconds of idle time, every 10 seconds, and gives up after 5 attempts.
The server runs as a subprocess via the `uv` command and communicates with Cursor through the MCP stdio transport. Authentication is passed as configuration parameters.

Local database MCP server: your agent sees a migration's impact before it runs, for PostgreSQL, MySQL, SQL Server and SQLite, with no database credentials.
A Model Context Protocol server that provides read-only access to MySQL databases. This server enables LLMs to inspect database schemas and execute read-only queries.

Model Context Protocol Servers

Oracle MCP server with no run-sql tool: It generates tools for each of the PL/SQL procedures, tables and approved SQL you choose. The server doesn't expose a SQL prompt, and can't reveal how it's connected to Oracle.
The official Redis MCP Server is a natural language interface designed for agentic applications to manage and search data in Redis efficiently
Comments