ClickHouse · Cursor
Add the ClickHouse MCP server to Cursor
Query and explore ClickHouse clusters and chDB.
1. Add the server
Paste into .cursor/mcp.json (project) or ~/.cursor/mcp.json (global)
{
"mcpServers": {
"clickhouse": {
"command": "uvx",
"args": [
"mcp-clickhouse"
],
"env": {
"CLICKHOUSE_HOST": "<your CLICKHOUSE_HOST>",
"CLICKHOUSE_USER": "<your CLICKHOUSE_USER>"
}
}
}
}Scopes, env vars, OAuth and limits: Cursor MCP config guide
2. Sign in
Cursor prompts you to sign in the first time a remote OAuth server is used. ClickHouse runs locally and needs CLICKHOUSE_HOST, CLICKHOUSE_USER. Replace the placeholder values above with your own before starting Cursor.
3. Try it
Ask Cursor for something ClickHouse can do. Query and explore ClickHouse clusters and chDB. Approve the first tool call and check the result before allowing write actions automatically.
- · Remote servers take a url; local servers take command and args.
- · Values can reference ${env:NAME} so secrets stay out of the file.
FAQ
- How do I add the ClickHouse MCP server to Cursor?
- Run: { …. Cursor prompts you to sign in the first time a remote OAuth server is used.
- Is this the official ClickHouse MCP server?
- Yes. It is published by ClickHouse as io.github.ClickHouse/mcp-clickhouse in the official MCP registry.
- Does the ClickHouse MCP server need an API key?
- Yes. It runs locally and requires CLICKHOUSE_HOST, CLICKHOUSE_USER.
Links
ClickHouse in other clients
More databases for Cursor
Built an MCP server? Get it listed everywhere →
Shipping an Android app? Google Play needs 12 testers for 14 days first. Get them with Tester Exchange →
Reviewed Oct 21, 2026. Command generated from the registry record and checked against Cursor's documented syntax.