MCP ClickHouse Tool
A read-only-by-default Model Context Protocol (MCP) server for ClickHouse with schema discovery, parameterized SELECT queries, execution-plan analysis, and opt-in writes per profile (coming soon). Profile-based configuration serves multiple databases and clusters from one toolset deployment.
Read-only is enforced by the engine, not by SQL text matching: every client carries ClickHouse's readonly=1, so writes, external table functions and query-level SETTINGS are refused by the server being queried. There is no write tool to opt into.
Requirements: Python 3.13+, a running ClickHouse instance, and connection details via environment variables or a config file.
Quick start
Set a DSN and run the server with MCP Inspector:
# Option 1: Run directly with uvx (no clone needed)
export MCP_CLICKHOUSE_DSN="http://default:@localhost:8123/default"
npx -y @modelcontextprotocol/inspector@latest uvx mcp-clickhousex
# Option 2: Run from source (clone repo, then)
export MCP_CLICKHOUSE_DSN="http://default:@localhost:8123/default"
npx -y @modelcontextprotocol/inspector@latest uv run mcp-clickhousex
Configuration
A profile is one ClickHouse connection: a DSN plus the row and timeout caps that apply to it. A profile named default always exists; every tool takes an optional profile to reach another, and list_profiles reports what is configured.
Settings come from three sources, merged field by field, later winning:
- the user-scoped
config.json— any number of profiles; MCP_CLICKHOUSE_PROFILES_<NAME>_<FIELD>environment variables — any number of profiles;- flat
MCP_CLICKHOUSE_<FIELD>environment variables — thedefaultprofile only.
Because the merge is per field rather than per profile, a config.json can carry the full set while a flat MCP_CLICKHOUSE_DSN repoints the default profile at a local server, leaving its other fields intact. With none of the three present, default falls back to http://default:@localhost:8123/default.
Each setting has one field name, spelled three ways — MCP_CLICKHOUSE_<FIELD>, MCP_CLICKHOUSE_PROFILES_<NAME>_<FIELD>, or the field lowercased as a JSON key:
| Field | Default | Hard ceiling |
|---|---|---|
DSN |
http://default:@localhost:8123/default |
— |
DESCRIPTION |
none | — |
QUERY_MAX_ROWS |
500 | 1 000 |
QUERY_COMMAND_TIMEOUT_SECONDS |
30 | 300 |
SNAPSHOT_MAX_ROWS |
10 000 | 50 000 |
SNAPSHOT_COMMAND_TIMEOUT_SECONDS |
120 | 300 |
Caps are per profile. A value above its ceiling is clamped at startup; a value that is not an integer falls back to the default.
Single connection: flat environment variables are the shortest path.
# Connection DSN.
export MCP_CLICKHOUSE_DSN="http://user:password@host:8123/database"
# Optional description for the default profile (tooling/AI discovery).
export MCP_CLICKHOUSE_DESCRIPTION="Primary cluster"
# Optional caps, defaults shown.
export MCP_CLICKHOUSE_QUERY_MAX_ROWS="500"
export MCP_CLICKHOUSE_QUERY_COMMAND_TIMEOUT_SECONDS="30"
export MCP_CLICKHOUSE_SNAPSHOT_MAX_ROWS="10000"
export MCP_CLICKHOUSE_SNAPSHOT_COMMAND_TIMEOUT_SECONDS="120"
Multiple connections: use the user-scoped config.json, which keeps credentials out of the host's process environment.
- Unix-like:
~/.config/mcp-clickhousex/config.json - Windows:
%USERPROFILE%\.config\mcp-clickhousex\config.json
{
"profiles": {
"default": {
"dsn": "http://default:@localhost:8123/default",
"description": "Primary",
"query_max_rows": 500,
"query_command_timeout_seconds": 60,
"snapshot_max_rows": 10000,
"snapshot_command_timeout_seconds": 120
},
"warehouse": {
"dsn": "http://user:pass@warehouse:8123/analytics",
"description": "Warehouse"
}
}
}
Profile names are case-insensitive and must be alphanumeric — no underscores or hyphens, since the structured env form splits on _ (MCP_CLICKHOUSE_PROFILES_WAREHOUSE_DSN is profile warehouse, field DSN). A name that breaks the rule is skipped, as is a config.json that is missing, unreadable, or not shaped {"profiles": {…}}; the server starts on whatever sources remain rather than failing.
DSN syntax: scheme://user:password@host:port/database. An https:// or clickhouses:// scheme enables TLS, and query-string parameters reach the driver (?connect_timeout=10) — except the read-only setting, which the server always applies last.
URL-reserved characters in the username or password must be percent-encoded — # → %23, ? → %3F, / → %2F, @ → %40, % → %25. Username admin@org with password p#ss? becomes http://admin%40org:p%23ss%3F@host:8123/database.
Tools and resources
All tools accept an optional profile; when omitted, the default profile is used.
Tools
| Tool | Description | Key params |
|---|---|---|
list_profiles |
List configured connection profiles. Call first when picking a non-default profile. | — |
run_query |
Execute one read-only SELECT (CTEs allowed) or SHOW statement. Returns rows inline as CSV, or a chx://snapshots/{id} URI when snapshot=true. Inline limit: 500 rows (hard ceiling 1 000). Snapshot limit: 10 000 rows (hard ceiling 50 000). No INTO OUTFILE. |
sql, parameters, database, profile, snapshot |
analyze_query |
EXPLAIN a read-only SELECT; returns plan, pipeline or syntax, no result rows. SHOW is not an EXPLAIN target. |
sql, parameters, database, profile, types |
types—EXPLAINvariants:plan(indexes),pipeline,syntax. Defaults toplanandpipeline.parameters— Named parameters for driver placeholders,%(name)sor{name:Type}.database— Session default database for unqualified names; otherwise qualify asdb.table.
Catalog discovery has no dedicated tool: list databases, tables and columns — and read sizes (total_rows, total_bytes) and keys (primary_key, sorting_key, partition_key) — with run_query over system.databases, system.tables and system.columns, which take ordinary WHERE predicates where SHOW takes only LIKE. SHOW earns its place for DDL a listing cannot give you — SHOW CREATE TABLE/VIEW/DICTIONARY for codecs, TTLs and the full column list.
Results are RFC 4180 CSV: the first row is the header, the rest are data. NULL is written as \N, ClickHouse's own CSV null representation, so it stays distinct from the empty string.
A plan's Indexes section is not authoritative about a table's keys: it names only the key columns the query used, so a query that skips the leading key column reports a shorter key than the table has. Confirm from system.tables, which answers in a few dozen tokens where SHOW CREATE TABLE spends several hundred to say the same thing.
The row caps that applied to a call arrive with its result as truncated and row_limit.
Resources
| URI | Description |
|---|---|
chx://profiles |
List configured connection profiles (application/json). Same data as list_profiles. |
chx://snapshots/{id} |
Fetch a query result snapshot as CSV; id comes from the snapshot_uri that run_query returns. Expires after 7 days. |
Security
Every client this server opens carries ClickHouse's own readonly=1, so the engine — not just the server's SQL checks — refuses:
- writes of any kind (
INSERT, DDL,ALTER … UPDATE,SYSTEM,GRANT); - the external table functions
url(),s3(),remote(),mysql()and friends, so a query cannot reach a host outside the configured profile; - query-level
SETTINGS, so the row and time caps cannot be raised by the SQL an agent supplies, andINTO OUTFILEis refused.
readonly=2 is deliberately not used: it permits SETTINGS changes, which would make those caps advisory. The tradeoff is that benign per-query tuning (SETTINGS max_threads = …) is refused too.
On top of that, run_query accepts SELECT / WITH … SELECT / SHOW and analyze_query only the first two, one statement per call. Interactive queries enforce a tight row cap (default 500, hard ceiling 1 000); for larger extracts use snapshot=true (default 10 000, hard ceiling 50 000). Use environment variables or the config file for connection credentials — never commit secrets.
MCP host examples
Snippets use uvx mcp-clickhousex (no clone required; ensure uv is on your PATH). Replace connection details as needed; the env block is unnecessary when the DSN already comes from config.json or the environment.
Claude Code and Cursor read the same mcpServers shape:
{
"mcpServers": {
"clickhouse": {
"command": "uvx",
"args": ["mcp-clickhousex"],
"env": {
"MCP_CLICKHOUSE_DSN": "http://default:@localhost:8123/default"
}
}
}
}
Codex, OpenCode and GitHub Copilot
Codex (TOML):
[mcp_servers.clickhouse]
command = "uvx"
args = ["mcp-clickhousex"]
[mcp_servers.clickhouse.env]
MCP_CLICKHOUSE_DSN = "http://default:@localhost:8123/default"
OpenCode:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"clickhouse": {
"type": "local",
"enabled": true,
"command": ["uvx", "mcp-clickhousex"],
"environment": {
"MCP_CLICKHOUSE_DSN": "http://default:@localhost:8123/default"
}
}
}
}
GitHub Copilot:
{
"inputs": [],
"servers": {
"clickhouse": {
"type": "stdio",
"command": "uvx",
"args": ["mcp-clickhousex"],
"env": {
"MCP_CLICKHOUSE_DSN": "http://default:@localhost:8123/default"
}
}
}
}
Tests
Tests require a running ClickHouse instance; the suite creates a sample table in the default database, seeds it, and drops it after.
uv run pytest tests/ -v
The harness locates the instance through MCP_TEST_CLICKHOUSE_DSN, falling back to http://admin:password123@localhost:8123/default. Set it to point tests at another server without touching your production MCP_CLICKHOUSE_DSN.
Contributing
Open issues or PRs; follow existing style and add tests where appropriate.
License
Release files for mcp-clickhousex 0.11.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mcp_clickhousex-0.11.0.tar.gz | 87.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_clickhousex-0.11.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 106.5 kB
Release files / mcp_clickhousex-0.11.0.tar.gz
| Download URL | mcp_clickhousex-0.11.0.tar.gz |
|---|---|
| Size | 87.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3afd4d5ec9e8f997f727da041c9af0ec8ef7c29648e85dad956d254c8bdf665c
|
|
BLAKE2b-256 checksum How to use checksums |
fec52d769d1ba1e94d1bd93404ead2fd9cc5dd3fd015e0e7b7631cc8a98d2f02
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 20, 2026.
Transparency logRelease files / mcp_clickhousex-0.11.0-py3-none-any.whl
| Download URL | mcp_clickhousex-0.11.0-py3-none-any.whl |
|---|---|
| Size | 19.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e11d1269ec3e4159a06a9f99cb0f28f27d500de3464adfaf9e37859bd6b65109
|
|
BLAKE2b-256 checksum How to use checksums |
35fbf3a1b96001d00bd47bfcf729bdf29394f950e7fd33213b4221c970bffc9a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 20, 2026.
Transparency log