ClickHouse
Lets an agent run SQL, inspect databases and tables in ClickHouse, and query external data with chDB. Summary written by AI Index.
The registry’s description: Official ClickHouse MCP server for querying and exploring ClickHouse clusters and chDB.
CLICKHOUSE_HOST, CLICKHOUSE_USER Add to your client
Add the ClickHouse MCP server to Claude Code
Run the command
claude mcp add -e CLICKHOUSE_HOST=<CLICKHOUSE_HOST> -e CLICKHOUSE_USER=<CLICKHOUSE_USER> clickhouse -- uvx mcp-clickhouseFill in the values ↓
Check it’s connected
Add the ClickHouse MCP server to Cursor
Open mcp.json· Where the file is:
~/.cursor/mcp.json,.cursor/mcp.jsonPaste the server entry
{ "mcpServers": { "clickhouse": { "command": "uvx", "args": [ "mcp-clickhouse" ], "env": { "CLICKHOUSE_HOST": "<CLICKHOUSE_HOST>", "CLICKHOUSE_USER": "<CLICKHOUSE_USER>" } } } }Fill in the values ↓
Check it’s connected
Add the ClickHouse MCP server to VS Code
Open mcp.json· Where the file is:
.vscode/mcp.jsonPaste the server entry
{ "servers": { "clickhouse": { "command": "uvx", "args": [ "mcp-clickhouse" ], "env": { "CLICKHOUSE_HOST": "<CLICKHOUSE_HOST>", "CLICKHOUSE_USER": "<CLICKHOUSE_USER>" } } } }Fill in the values ↓
Check it’s connected
Add the ClickHouse MCP server to Codex
Run the command
codex mcp add clickhouse --env CLICKHOUSE_HOST=<CLICKHOUSE_HOST> --env CLICKHOUSE_USER=<CLICKHOUSE_USER> -- uvx mcp-clickhouseFill in the values ↓
Check it’s connected
Add the ClickHouse MCP server to Devin Desktop
Open mcp_config.json· Where the file is:
~/.config/devin/mcp_config.json,%APPDATA%\devin\mcp_config.jsonPaste the server entry
{ "mcpServers": { "clickhouse": { "command": "uvx", "args": [ "mcp-clickhouse" ], "env": { "CLICKHOUSE_HOST": "<CLICKHOUSE_HOST>", "CLICKHOUSE_USER": "<CLICKHOUSE_USER>" } } } }Fill in the values ↓
Check it’s connected
Add the ClickHouse MCP server to Gemini CLI
Open settings.json· Where the file is:
~/.gemini/settings.json,.gemini/settings.jsonPaste the server entry
{ "mcpServers": { "clickhouse": { "command": "uvx", "args": [ "mcp-clickhouse" ], "env": { "CLICKHOUSE_HOST": "<CLICKHOUSE_HOST>", "CLICKHOUSE_USER": "<CLICKHOUSE_USER>" } } } }Fill in the values ↓
Check it’s connected
Add the ClickHouse MCP server to GitHub Copilot
Run the command
copilot mcp add --env CLICKHOUSE_HOST=<CLICKHOUSE_HOST> --env CLICKHOUSE_USER=<CLICKHOUSE_USER> clickhouse -- uvx mcp-clickhouseFill in the values ↓
Check it’s connected
Add the ClickHouse MCP server to Cline
Open cline_mcp_settings.json· Where the file is:
~/.cline/data/settings/cline_mcp_settings.jsonPaste the server entry
{ "mcpServers": { "clickhouse": { "command": "uvx", "args": [ "mcp-clickhouse" ], "env": { "CLICKHOUSE_HOST": "<CLICKHOUSE_HOST>", "CLICKHOUSE_USER": "<CLICKHOUSE_USER>" } } } }Fill in the values ↓
Check it’s connected
Add the ClickHouse MCP server to Kiro
Open mcp.json· Where the file is:
.kiro/settings/mcp.json,~/.kiro/settings/mcp.jsonPaste the server entry
{ "mcpServers": { "clickhouse": { "command": "uvx", "args": [ "mcp-clickhouse" ], "env": { "CLICKHOUSE_HOST": "<CLICKHOUSE_HOST>", "CLICKHOUSE_USER": "<CLICKHOUSE_USER>" } } } }Fill in the values ↓
Check it’s connected
Add the ClickHouse MCP server to Zed
Open settings.json
Paste the server entry
{ "context_servers": { "clickhouse": { "command": "uvx", "args": [ "mcp-clickhouse" ], "env": { "CLICKHOUSE_HOST": "<CLICKHOUSE_HOST>", "CLICKHOUSE_USER": "<CLICKHOUSE_USER>" } } } }Fill in the values ↓
Check it’s connected
Add the ClickHouse MCP server to OpenCode
Open opencode.json· Where the file is:
~/.config/opencode/opencode.json,opencode.jsonPaste the server entry
{ "$schema": "https://opencode.ai/config.json", "mcp": { "clickhouse": { "type": "local", "command": [ "uvx", "mcp-clickhouse" ], "enabled": true, "environment": { "CLICKHOUSE_HOST": "<CLICKHOUSE_HOST>", "CLICKHOUSE_USER": "<CLICKHOUSE_USER>" } } } }Fill in the values ↓
Check it’s connected
Add the ClickHouse MCP server to JetBrains AI Assistant
Open JetBrains AI Assistant’s MCP config
- Open Settings | Tools | AI Assistant | Model Context Protocol (MCP).
- Choose Add.
Paste the server entry
{ "mcpServers": { "clickhouse": { "command": "uvx", "args": [ "mcp-clickhouse" ] } } }Check it’s connected
This client’s docs give no way to pass these values here; set them as the server’s documentation says.
If the file already has servers, add the entry inside the existing object. To check it’s connected, restart or reload the client and look for clickhouse in its list of MCP servers. A server that needs sign-in opens it on first use.
What you fill in
Required values appear as <NAME> placeholders in the snippets; add optional ones the same way. Descriptions are the server’s registry entry’s.
<CLICKHOUSE_HOST>Environment variable RequiredHostname of the ClickHouse server
<CLICKHOUSE_USER>Environment variable RequiredUsername for ClickHouse authentication
<CLICKHOUSE_PASSWORD>Environment variable Optional · SecretPassword for ClickHouse authentication. Required unless a client certificate uses the default or mutual TLS mode
<CLICKHOUSE_PORT>Environment variable OptionalClickHouse HTTP(S) port. Defaults to 8443 when CLICKHOUSE_SECURE=true, 8123 otherwise
<CLICKHOUSE_SECURE>Environment variable OptionalUse HTTPS to connect to ClickHouse
<CLICKHOUSE_VERIFY>Environment variable OptionalVerify SSL certificates
<CLICKHOUSE_CA_CERT>Environment variable OptionalPath to a PEM CA bundle for ClickHouse server certificate verification
<CLICKHOUSE_CLIENT_CERT>Environment variable OptionalPath to a PEM client certificate for the ClickHouse HTTPS connection
<CLICKHOUSE_CLIENT_CERT_KEY>Environment variable OptionalPath to the PEM private key for CLICKHOUSE_CLIENT_CERT
<CLICKHOUSE_TLS_MODE>Environment variable OptionalClient certificate mode: mutual, proxy, or strict
<CLICKHOUSE_DATABASE>Environment variable OptionalDefault database to use
<CLICKHOUSE_ROLE>Environment variable OptionalClickHouse role to activate for the session
<CLICKHOUSE_ALLOW_WRITE_ACCESS>Environment variable OptionalAllow write operations (DDL and DML). Queries run read-only by default
<CLICKHOUSE_ALLOW_DROP>Environment variable OptionalAllow destructive operations (DROP, TRUNCATE, DELETE, UPDATE, REPLACE, CLEAR, and DETACH PERMANENTLY) when write access is also enabled
<CLICKHOUSE_MCP_QUERY_TIMEOUT>Environment variable OptionalQuery tool timeout in seconds
<CLICKHOUSE_MCP_MAX_WORKERS>Environment variable OptionalMaximum query worker thread pool size
Client compatibility
By transport: whether the client’s docs list a transport this server offers. It doesn’t cover sign-in or other requirements.
- Claude Code Transport supported
- Cursor Transport supported
- VS Code Client docs don’t list transports
- Codex Transport supported
- Devin Desktop Transport supported
- Gemini CLI Transport supported
- GitHub Copilot Client docs don’t list transports
- Cline Transport supported
- Kiro Transport supported
- Zed Client docs don’t list transports
- OpenCode Client docs don’t list transports
- JetBrains AI Assistant Transport supported
- Claude Client docs don’t list transports
- ChatGPT No shared transport
Agent Skills: ClickHouse
clickhouse-architecture-advisor, clickhouse-best-practices, chdb-datastore, chdb-sql, clickstack-otel-collector, ClickHouse, infra-clickhouse, infra-postgres, clickhouse-js-node-troubleshooting, clickhouse
Sources
- Official MCP Registry registry.modelcontextprotocol.io · checked Nov 4, 2026
- GitHub organization ClickHouse (verified domain) github.com · checked Nov 4, 2026
This data comes from the Official MCP Registry.