ClickHouse

Official ClickHouse Data & databases

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.

Local package (pypi) Needs a value: CLICKHOUSE_HOST, CLICKHOUSE_USER

Add to your client

Add the ClickHouse MCP server to Claude Code

  1. Run the command

    claude mcp add -e CLICKHOUSE_HOST=<CLICKHOUSE_HOST> -e CLICKHOUSE_USER=<CLICKHOUSE_USER> clickhouse -- uvx mcp-clickhouse
  2. Fill in the values ↓

  3. Check it’s connected

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 Required

    Hostname of the ClickHouse server

  • <CLICKHOUSE_USER> Environment variable Required

    Username for ClickHouse authentication

  • <CLICKHOUSE_PASSWORD> Environment variable Optional · Secret

    Password for ClickHouse authentication. Required unless a client certificate uses the default or mutual TLS mode

  • <CLICKHOUSE_PORT> Environment variable Optional

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

  • <CLICKHOUSE_SECURE> Environment variable Optional

    Use HTTPS to connect to ClickHouse

  • <CLICKHOUSE_VERIFY> Environment variable Optional

    Verify SSL certificates

  • <CLICKHOUSE_CA_CERT> Environment variable Optional

    Path to a PEM CA bundle for ClickHouse server certificate verification

  • <CLICKHOUSE_CLIENT_CERT> Environment variable Optional

    Path to a PEM client certificate for the ClickHouse HTTPS connection

  • <CLICKHOUSE_CLIENT_CERT_KEY> Environment variable Optional

    Path to the PEM private key for CLICKHOUSE_CLIENT_CERT

  • <CLICKHOUSE_TLS_MODE> Environment variable Optional

    Client certificate mode: mutual, proxy, or strict

  • <CLICKHOUSE_DATABASE> Environment variable Optional

    Default database to use

  • <CLICKHOUSE_ROLE> Environment variable Optional

    ClickHouse role to activate for the session

  • <CLICKHOUSE_ALLOW_WRITE_ACCESS> Environment variable Optional

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

  • <CLICKHOUSE_ALLOW_DROP> Environment variable Optional

    Allow destructive operations (DROP, TRUNCATE, DELETE, UPDATE, REPLACE, CLEAR, and DETACH PERMANENTLY) when write access is also enabled

  • <CLICKHOUSE_MCP_QUERY_TIMEOUT> Environment variable Optional

    Query tool timeout in seconds

  • <CLICKHOUSE_MCP_MAX_WORKERS> Environment variable Optional

    Maximum 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.

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

This data comes from the Official MCP Registry.