Ext Ops Panel
Open dashboard

What it can do: ClickHouse

MCP server · ClickHouse

What ClickHouse declares, asks for and runs, according to the marketplaces we read. Runs on your machine: the AI tool starts this PyPI package locally: mcp-clickhouse. Tools it declares: 3. Environment variables it asks for: 16, secrets among them: 1. As of our marketplace pass on 2026-10-12.

This is not a security audit. We list what the marketplaces publish about this plugin: what it declares, what it asks for and what it runs. We do not run or inspect its code, and a verified mark is the marketplace's statement, not ours.

Where it runs

  • Runs on your machine: the AI tool starts this PyPI package locally: mcp-clickhouseAs declared on: Official MCP Registry.
  • Runs on your machine, in a container started from this image: mcp/clickhouseAs declared on: Docker MCP Catalog.

What it declares

Tools it declares: 3. As declared on: Docker MCP Catalog.

  • list_databases
  • list_tables
  • run_select_query

Prompts and resources: the marketplaces we read do not publish them.

What it asks for

Environment variables it asks for: 16, secrets among them: 1. As declared on: Official MCP Registry.

  • CLICKHOUSE_ALLOW_DROP
  • CLICKHOUSE_ALLOW_WRITE_ACCESS
  • CLICKHOUSE_CA_CERT
  • CLICKHOUSE_CLIENT_CERT
  • CLICKHOUSE_CLIENT_CERT_KEY
  • CLICKHOUSE_DATABASE
  • CLICKHOUSE_HOST required
  • CLICKHOUSE_MCP_MAX_WORKERS
  • CLICKHOUSE_MCP_QUERY_TIMEOUT
  • CLICKHOUSE_PASSWORD secret
  • CLICKHOUSE_PORT
  • CLICKHOUSE_ROLE
Show the remaining 4
  • CLICKHOUSE_SECURE
  • CLICKHOUSE_TLS_MODE
  • CLICKHOUSE_USER required
  • CLICKHOUSE_VERIFY

Environment variables it asks for: 8, secrets among them: 1. As declared on: Docker MCP Catalog.

  • CLICKHOUSE_CONNECT_TIMEOUT
  • CLICKHOUSE_HOST
  • CLICKHOUSE_PASSWORD secret required
  • CLICKHOUSE_PORT
  • CLICKHOUSE_SECURE
  • CLICKHOUSE_SEND_RECEIVE_TIMEOUT
  • CLICKHOUSE_USER
  • CLICKHOUSE_VERIFY

Names only: we keep no values, examples or descriptions of these variables. OAuth scopes and install-time settings are not published by the marketplaces we read.

What it runs besides MCP

None of the marketplaces we read lists hooks, commands, agents or language servers for it.

Who answers for it

ClickHouse

  • No marketplace we read marks it or its publisher as verified.
  • License: Apache-2.0.
  • Last change we saw: 2026-10-12.
  • The repository github.com/clickhouse/mcp-clickhouse belongs to the account the publisher is listed under on Official MCP Registry.

How it has changed

Its tools, settings, hooks and composition have not changed since we started watching it.

In context

  • Median number of secrets an MCP server asks for on the marketplaces we read: 0.0. This one asks for: 1.
  • Share of MCP servers that run on a remote server: 63%.

Where it is published and how its figures have moved

Compare it side by side with similar plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built