← Index

ClickHouse

io.github.ClickHouse/mcp-clickhousev0.5.0Databases

Official ClickHouse MCP server for querying and exploring ClickHouse clusters and chDB.

The current version, v0.5.0, was published to the official MCP registry on 2026-09-01. It is distributed as mcp-clickhouse on PyPI and as the Docker image ghcr.io/clickhouse/mcp-clickhouse:0.5.0, filed under Databases by this index, and declares 12 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using ClickHouse in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
REVIEWstatus: PARTIALfresh until 2026-09-09 00:18 UTC
screened 2026-07-24tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidenceNo malicious instructions foundvia static_description

Limits of this verdict
  • - Semantic screen only - the deterministic conformance probe has not run on this server
  • - Confidence is reported but not yet calibrated (v1)
  • - Screen reads the tool description, not the live behavior
  • - advisory
  • - registry description only no input schema
  • - screen model 8b
  • - Still current: the description we screened is unchanged, re-checked against the registry
  • - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-09-02).

Contracts can change after screening, with no version bump. The gate pins ClickHouse’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Cite this record

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

Markdown
[Independent trust record for ClickHouse](https://mcpindex.ai/server/io-github-clickhouse-mcp-clickhouse) - screening verdict, registry provenance, and contract drift monitoring.
HTML
<a href="https://mcpindex.ai/server/io-github-clickhouse-mcp-clickhouse">Independent trust record for ClickHouse</a> - screening verdict, registry provenance, and contract drift monitoring.
Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown
[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-clickhouse-mcp-clickhouse)](https://mcpindex.ai/server/io-github-clickhouse-mcp-clickhouse)
HTML
<a href="https://mcpindex.ai/server/io-github-clickhouse-mcp-clickhouse"><img src="https://mcpindex.ai/api/v1/badge/io-github-clickhouse-mcp-clickhouse" alt="mcpindex verdict" height="20" /></a>
Environment variables
CLICKHOUSE_HOST
required

Hostname of the ClickHouse server

CLICKHOUSE_USER
required

Username for ClickHouse authentication

CLICKHOUSE_PASSWORD
requiredsecret

Password for ClickHouse authentication

CLICKHOUSE_PORT

ClickHouse HTTP(S) port. Defaults to 8443 when CLICKHOUSE_SECURE=true, 8123 otherwise

CLICKHOUSE_SECURE

Use HTTPS to connect to ClickHouse

CLICKHOUSE_VERIFY

Verify SSL certificates

CLICKHOUSE_DATABASE

Default database to use

CLICKHOUSE_ROLE

ClickHouse role to activate for the session

CLICKHOUSE_ALLOW_WRITE_ACCESS

Allow write operations (DDL and DML). Queries run read-only by default

CLICKHOUSE_ALLOW_DROP

Allow destructive operations (DROP, TRUNCATE) when write access is also enabled

CLICKHOUSE_MCP_QUERY_TIMEOUT

Query tool timeout in seconds

CLICKHOUSE_MCP_MAX_WORKERS

Maximum query worker thread pool size

CLICKHOUSE_HOST
required

Hostname of the ClickHouse server

CLICKHOUSE_USER
required

Username for ClickHouse authentication

CLICKHOUSE_PASSWORD
requiredsecret

Password for ClickHouse authentication

CLICKHOUSE_PORT

ClickHouse HTTP(S) port. Defaults to 8443 when CLICKHOUSE_SECURE=true, 8123 otherwise

CLICKHOUSE_SECURE

Use HTTPS to connect to ClickHouse

CLICKHOUSE_VERIFY

Verify SSL certificates

CLICKHOUSE_DATABASE

Default database to use

CLICKHOUSE_ROLE

ClickHouse role to activate for the session

CLICKHOUSE_ALLOW_WRITE_ACCESS

Allow write operations (DDL and DML). Queries run read-only by default

CLICKHOUSE_ALLOW_DROP

Allow destructive operations (DROP, TRUNCATE) when write access is also enabled

CLICKHOUSE_MCP_QUERY_TIMEOUT

Query tool timeout in seconds

CLICKHOUSE_MCP_MAX_WORKERS

Maximum query worker thread pool size

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
20
installability
25
documentation
15
stability
5
Alternatives in Databases