ClickHouse for Gemini CLI

io.github.clickhouse/mcp-clickhouse

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

client:Gemini CLI transport:stdio runtime:pypi

Install ClickHouse in Gemini CLI

~/.gemini/settings.json · windows: %USERPROFILE%\.gemini\settings.json

CLICKHOUSE_HOST

CLICKHOUSE_USER

CLICKHOUSE_PASSWORD

CLICKHOUSE_PORT

CLICKHOUSE_SECURE

CLICKHOUSE_VERIFY

CLICKHOUSE_CA_CERT

CLICKHOUSE_CLIENT_CERT

CLICKHOUSE_CLIENT_CERT_KEY

CLICKHOUSE_TLS_MODE

CLICKHOUSE_DATABASE

CLICKHOUSE_ROLE

CLICKHOUSE_ALLOW_WRITE_ACCESS

CLICKHOUSE_ALLOW_DROP

CLICKHOUSE_MCP_QUERY_TIMEOUT

CLICKHOUSE_MCP_MAX_WORKERS

Held in this page only — never stored, logged, or sent anywhere but back to your screen.

{
  "mcpServers": {
    "mcp-clickhouse": {
      "command": "uvx",
      "args": [
        "mcp-clickhouse"
      ],
      "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>"
      }
    }
  }
}

Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs

ClickHouse in other clients

ClickHouse MCP server