Official ClickHouse MCP server for querying and exploring ClickHouse clusters and chDB.
Connect Runs on your machine
claude mcp add mcp-clickhouse -e CLICKHOUSE_HOST=<CLICKHOUSE_HOST> -e CLICKHOUSE_USER=<CLICKHOUSE_USER> -e CLICKHOUSE_PASSWORD=<CLICKHOUSE_PASSWORD> -e CLICKHOUSE_PORT=<CLICKHOUSE_PORT> -e CLICKHOUSE_SECURE=<CLICKHOUSE_SECURE> -e CLICKHOUSE_VERIFY=<CLICKHOUSE_VERIFY> -e CLICKHOUSE_CA_CERT=<CLICKHOUSE_CA_CERT> -e CLICKHOUSE_CLIENT_CERT=<CLICKHOUSE_CLIENT_CERT> -e CLICKHOUSE_CLIENT_CERT_KEY=<CLICKHOUSE_CLIENT_CERT_KEY> -e CLICKHOUSE_TLS_MODE=<CLICKHOUSE_TLS_MODE> -e CLICKHOUSE_DATABASE=<CLICKHOUSE_DATABASE> -e CLICKHOUSE_ROLE=<CLICKHOUSE_ROLE> -e CLICKHOUSE_ALLOW_WRITE_ACCESS=<CLICKHOUSE_ALLOW_WRITE_ACCESS> -e CLICKHOUSE_ALLOW_DROP=<CLICKHOUSE_ALLOW_DROP> -e CLICKHOUSE_MCP_QUERY_TIMEOUT=<CLICKHOUSE_MCP_QUERY_TIMEOUT> -e CLICKHOUSE_MCP_MAX_WORKERS=<CLICKHOUSE_MCP_MAX_WORKERS> -- uvx mcp-clickhouse==0.7.0
{
"mcpServers": {
"mcp-clickhouse": {
"command": "uvx",
"args": [
"mcp-clickhouse==0.7.0"
],
"env": {
"CLICKHOUSE_HOST": "<CLICKHOUSE_HOST>",
"CLICKHOUSE_USER": "<CLICKHOUSE_USER>",
"CLICKHOUSE_PASSWORD": "<CLICKHOUSE_PASSWORD>",
"CLICKHOUSE_PORT": "<CLICKHOUSE_PORT>",
"CLICKHOUSE_SECURE": "<CLICKHOUSE_SECURE>",
"CLICKHOUSE_VERIFY": "<CLICKHOUSE_VERIFY>",
"CLICKHOUSE_CA_CERT": "<CLICKHOUSE_CA_CERT>",
"CLICKHOUSE_CLIENT_CERT": "<CLICKHOUSE_CLIENT_CERT>",
"CLICKHOUSE_CLIENT_CERT_KEY": "<CLICKHOUSE_CLIENT_CERT_KEY>",
"CLICKHOUSE_TLS_MODE": "<CLICKHOUSE_TLS_MODE>",
"CLICKHOUSE_DATABASE": "<CLICKHOUSE_DATABASE>",
"CLICKHOUSE_ROLE": "<CLICKHOUSE_ROLE>",
"CLICKHOUSE_ALLOW_WRITE_ACCESS": "<CLICKHOUSE_ALLOW_WRITE_ACCESS>",
"CLICKHOUSE_ALLOW_DROP": "<CLICKHOUSE_ALLOW_DROP>",
"CLICKHOUSE_MCP_QUERY_TIMEOUT": "<CLICKHOUSE_MCP_QUERY_TIMEOUT>",
"CLICKHOUSE_MCP_MAX_WORKERS": "<CLICKHOUSE_MCP_MAX_WORKERS>"
}
}
}
}
{
"mcpServers": {
"mcp-clickhouse": {
"command": "uvx",
"args": [
"mcp-clickhouse==0.7.0"
],
"env": {
"CLICKHOUSE_HOST": "<CLICKHOUSE_HOST>",
"CLICKHOUSE_USER": "<CLICKHOUSE_USER>",
"CLICKHOUSE_PASSWORD": "<CLICKHOUSE_PASSWORD>",
"CLICKHOUSE_PORT": "<CLICKHOUSE_PORT>",
"CLICKHOUSE_SECURE": "<CLICKHOUSE_SECURE>",
"CLICKHOUSE_VERIFY": "<CLICKHOUSE_VERIFY>",
"CLICKHOUSE_CA_CERT": "<CLICKHOUSE_CA_CERT>",
"CLICKHOUSE_CLIENT_CERT": "<CLICKHOUSE_CLIENT_CERT>",
"CLICKHOUSE_CLIENT_CERT_KEY": "<CLICKHOUSE_CLIENT_CERT_KEY>",
"CLICKHOUSE_TLS_MODE": "<CLICKHOUSE_TLS_MODE>",
"CLICKHOUSE_DATABASE": "<CLICKHOUSE_DATABASE>",
"CLICKHOUSE_ROLE": "<CLICKHOUSE_ROLE>",
"CLICKHOUSE_ALLOW_WRITE_ACCESS": "<CLICKHOUSE_ALLOW_WRITE_ACCESS>",
"CLICKHOUSE_ALLOW_DROP": "<CLICKHOUSE_ALLOW_DROP>",
"CLICKHOUSE_MCP_QUERY_TIMEOUT": "<CLICKHOUSE_MCP_QUERY_TIMEOUT>",
"CLICKHOUSE_MCP_MAX_WORKERS": "<CLICKHOUSE_MCP_MAX_WORKERS>"
}
}
}
}
{
"servers": {
"mcp-clickhouse": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-clickhouse==0.7.0"
],
"env": {
"CLICKHOUSE_HOST": "<CLICKHOUSE_HOST>",
"CLICKHOUSE_USER": "<CLICKHOUSE_USER>",
"CLICKHOUSE_PASSWORD": "<CLICKHOUSE_PASSWORD>",
"CLICKHOUSE_PORT": "<CLICKHOUSE_PORT>",
"CLICKHOUSE_SECURE": "<CLICKHOUSE_SECURE>",
"CLICKHOUSE_VERIFY": "<CLICKHOUSE_VERIFY>",
"CLICKHOUSE_CA_CERT": "<CLICKHOUSE_CA_CERT>",
"CLICKHOUSE_CLIENT_CERT": "<CLICKHOUSE_CLIENT_CERT>",
"CLICKHOUSE_CLIENT_CERT_KEY": "<CLICKHOUSE_CLIENT_CERT_KEY>",
"CLICKHOUSE_TLS_MODE": "<CLICKHOUSE_TLS_MODE>",
"CLICKHOUSE_DATABASE": "<CLICKHOUSE_DATABASE>",
"CLICKHOUSE_ROLE": "<CLICKHOUSE_ROLE>",
"CLICKHOUSE_ALLOW_WRITE_ACCESS": "<CLICKHOUSE_ALLOW_WRITE_ACCESS>",
"CLICKHOUSE_ALLOW_DROP": "<CLICKHOUSE_ALLOW_DROP>",
"CLICKHOUSE_MCP_QUERY_TIMEOUT": "<CLICKHOUSE_MCP_QUERY_TIMEOUT>",
"CLICKHOUSE_MCP_MAX_WORKERS": "<CLICKHOUSE_MCP_MAX_WORKERS>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
CLICKHOUSE_HOSTRequired | Hostname of the ClickHouse server |
CLICKHOUSE_USERRequired | Username for ClickHouse authentication |
CLICKHOUSE_PASSWORDOptional, secret | Password for ClickHouse authentication. Required unless a client certificate uses the default or mutual TLS mode |
CLICKHOUSE_PORTOptional | ClickHouse HTTP(S) port. Defaults to 8443 when CLICKHOUSE_SECURE=true, 8123 otherwise |
CLICKHOUSE_SECUREOptional | Use HTTPS to connect to ClickHouse |
CLICKHOUSE_VERIFYOptional | Verify SSL certificates |
CLICKHOUSE_CA_CERTOptional | Path to a PEM CA bundle for ClickHouse server certificate verification |
CLICKHOUSE_CLIENT_CERTOptional | Path to a PEM client certificate for the ClickHouse HTTPS connection |
CLICKHOUSE_CLIENT_CERT_KEYOptional | Path to the PEM private key for CLICKHOUSE_CLIENT_CERT |
CLICKHOUSE_TLS_MODEOptional | Client certificate mode: mutual, proxy, or strict |
CLICKHOUSE_DATABASEOptional | Default database to use |
CLICKHOUSE_ROLEOptional | ClickHouse role to activate for the session |
CLICKHOUSE_ALLOW_WRITE_ACCESSOptional | Allow write operations (DDL and DML). Queries run read-only by default |
CLICKHOUSE_ALLOW_DROPOptional | Allow destructive operations (DROP, TRUNCATE, DELETE, UPDATE, REPLACE, CLEAR, and DETACH PERMANENTLY) when write access is also enabled |
CLICKHOUSE_MCP_QUERY_TIMEOUTOptional | Query tool timeout in seconds |
CLICKHOUSE_MCP_MAX_WORKERSOptional | Maximum query worker thread pool size |
Details
| Package | [email protected] (PYPI, stdio) |
| Package | ghcr.io/clickhouse/mcp-clickhouse:0.7.0 (OCI, stdio) |
| First published | 21 Sep 2026 |
| Last updated | 21 Sep 2026 |
| Registry name | io.github.ClickHouse/mcp-clickhouse |
More databases servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
