freemcplab / Directory / Playground / ClickHouse MCP

● Official clickhouse ⚡ Instant

ClickHouse MCP

Name: ClickHouse MCP MCP Server
Author: clickhouse

by clickhouse · ClickHouse/mcp-clickhouse

Connect ClickHouse columnar database to AI assistants — query analytical workloads through MCP.

ClickHouse MCP is an MCP server maintained by clickhouse. Connect ClickHouse columnar database to AI assistants — query analytical workloads through MCP. See README for installation and configuration: https://github.com/ClickHouse/mcp-clickhouse

▶ Watch demo 📦 Install 💡 Use Cases

Why use it

Key features

Connect ClickHouse columnar database to AI assistants — query analytical workloads through MCP.
Language: Python
777+ GitHub stars at verification time
Official / first-party project

Live Demo

What it looks like in practice

clickhouse-mcp.replay ▶ ready

0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "clickhouse-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-clickhouse"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "clickhouse-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-clickhouse"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "clickhouse-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-clickhouse"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "clickhouse-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-clickhouse"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "clickhouse-mcp",
      "command": "npx",
      "args": [
        "-y",
        "mcp-clickhouse"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "clickhouse-mcp": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "mcp-clickhouse"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add clickhouse-mcp -- npx -y mcp-clickhouse

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use ClickHouse MCP

Use ClickHouse MCP for its primary workflow

👤 Claude/MCP client users ⏱ ~20 min intermediate

When to use: See repo README for canonical use cases.

Prerequisites

Repo cloned or installed — See undefined

Flow

Install

Install ClickHouse MCP per README.✓ Copied

→ Tool registered with client
Configure

Provide credentials/config as instructed.✓ Copied

→ Successful auth/init
Use

Run a sample task with ClickHouse MCP.✓ Copied

→ Expected output

Outcome: You can drive the documented workflow end-to-end.

Pitfalls

Skipping README — Read the repo README and CHANGELOG before shipping to prod.

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
primary	see README	Primary action	free

Cost & Limits

What this costs to run

API quota: None of its own; bounded by upstream provider quotas if any
Tokens per call: Depends on usage
Monetary: Open source — check repo LICENSE
Tip: Review upstream API costs (if any) before automating.

Security

Permissions, secrets, blast radius

Minimum scopes: Whatever the upstream provider requires

Credential storage: Env vars or local config — never commit secrets

Data egress: Forwards data per its README

Never grant: Full admin to untrusted prompts

Project moves fast — pin a version in production.

Troubleshooting

Common errors and fixes

Auth fails

Verify credentials and required scopes match README.

Verify: Re-read repo README auth section.

Tool not found by client

Ensure MCP client config points to correct command/path.

Verify: Restart the client after editing config.

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills