ClickHousevf.sr
listing.by · home.legend.verified
Run read-only SQL and explore databases and tables on any ClickHouse cluster or in the embedded chDB engine.
listing.install
listing.local.explain
listing.local.needs listing.local.note
CLICKHOUSE_HOSTHostname of the ClickHouse serverCLICKHOUSE_USERUsername for ClickHouse authenticationCLICKHOUSE_PASSWORDlisting.env.secret listing.env.optional Password for ClickHouse authentication. Required unless a client certificate uses the default or mutual TLS modeCLICKHOUSE_PORTlisting.env.optional ClickHouse HTTP(S) port. Defaults to 8443 when CLICKHOUSE_SECURE=true, 8123 otherwiseCLICKHOUSE_SECURElisting.env.optional Use HTTPS to connect to ClickHouseCLICKHOUSE_VERIFYlisting.env.optional Verify SSL certificates
listing.share.h
listing.share.p_local
mcp.tc/i/clickhouselisting.about
Connects an assistant to a ClickHouse cluster or to chDB, the embedded ClickHouse engine. It can run SQL queries, list databases, list tables with pagination and filters, and run SELECT queries through chDB. Queries are read-only by default, and writes can be enabled explicitly. Parameterized queries with typed placeholders are supported.
Runs locally over stdio with uvx mcp-clickhouse (PyPI package), or as the ghcr.io/clickhouse/mcp-clickhouse container image. It needs CLICKHOUSE_HOST and CLICKHOUSE_USER, plus CLICKHOUSE_PASSWORD unless a client certificate is used. Optional variables set the port, TLS options, default database and role.
listing.can
- Run SQL queries on a ClickHouse cluster, read-only by default
- List all databases on the cluster
- List tables in a database with LIKE filters and pagination
- Bind typed query parameters with ClickHouse placeholders
- Check a query with DESCRIBE or EXPLAIN ESTIMATE before running it
- Run SELECT queries on the embedded chDB engine
listing.tools
listing.notools.key
listing.prompts
List all databases on my ClickHouse cluster.
Show the tables in the analytics database that start with events_.
Count rows per day in default.events for the last 30 days.
Estimate how many rows this query would read before running it.
listing.setup.h
listing.setup.local
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport stdio clickhouse --env "CLICKHOUSE_HOST=<YOUR_CLICKHOUSE_HOST>" --env "CLICKHOUSE_USER=<YOUR_CLICKHOUSE_USER>" --env "CLICKHOUSE_PASSWORD=<YOUR_CLICKHOUSE_PASSWORD>" -- uvx mcp-clickhouse- Start Claude Code and type
/mcp. clickhouse should show as connected.
Add --scope user to make it available in every project. Replace the placeholders with your own values.
Claude Desktop
- Open Settings → Developer → Edit Config. It opens
claude_desktop_config.json. Add:
{
"mcpServers": {
"clickhouse": {
"command": "uvx",
"args": [
"mcp-clickhouse"
],
"env": {
"CLICKHOUSE_HOST": "<YOUR_CLICKHOUSE_HOST>",
"CLICKHOUSE_USER": "<YOUR_CLICKHOUSE_USER>",
"CLICKHOUSE_PASSWORD": "<YOUR_CLICKHOUSE_PASSWORD>"
}
}
}
}- Save the file and restart Claude Desktop. Replace the placeholders with your own values.
Needs uv (Python) on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.
Cursor
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"clickhouse": {
"command": "uvx",
"args": [
"mcp-clickhouse"
],
"env": {
"CLICKHOUSE_HOST": "<YOUR_CLICKHOUSE_HOST>",
"CLICKHOUSE_USER": "<YOUR_CLICKHOUSE_USER>",
"CLICKHOUSE_PASSWORD": "<YOUR_CLICKHOUSE_PASSWORD>"
}
}
}
}Needs uv (Python) on your computer. Replace the placeholders with your own values.
VS Code
Add it to .vscode/mcp.json. VS Code asks for the secret the first time and stores it securely:
{
"servers": {
"clickhouse": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-clickhouse"
],
"env": {
"CLICKHOUSE_HOST": "<YOUR_CLICKHOUSE_HOST>",
"CLICKHOUSE_USER": "<YOUR_CLICKHOUSE_USER>",
"CLICKHOUSE_PASSWORD": "${input:clickhouse-password}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "clickhouse-password",
"description": "CLICKHOUSE_PASSWORD",
"password": true
}
]
}Needs uv (Python) on your computer.
Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"clickhouse": {
"command": "uvx",
"args": [
"mcp-clickhouse"
],
"env": {
"CLICKHOUSE_HOST": "<YOUR_CLICKHOUSE_HOST>",
"CLICKHOUSE_USER": "<YOUR_CLICKHOUSE_USER>",
"CLICKHOUSE_PASSWORD": "<YOUR_CLICKHOUSE_PASSWORD>"
}
}
}
}- Refresh the MCP server list in Cascade. Replace the placeholders with your own values.
Devin Desktop is the new name for Windsurf.
Codex
codex mcp add clickhouse --env "CLICKHOUSE_HOST=<YOUR_CLICKHOUSE_HOST>" --env "CLICKHOUSE_USER=<YOUR_CLICKHOUSE_USER>" --env "CLICKHOUSE_PASSWORD=<YOUR_CLICKHOUSE_PASSWORD>" -- uvx mcp-clickhouseOr edit ~/.codex/config.toml directly:
[mcp_servers.clickhouse]
command = "uvx"
args = ["mcp-clickhouse"]
env = { CLICKHOUSE_HOST = "<YOUR_CLICKHOUSE_HOST>", CLICKHOUSE_USER = "<YOUR_CLICKHOUSE_USER>", CLICKHOUSE_PASSWORD = "<YOUR_CLICKHOUSE_PASSWORD>" }Needs uv (Python) on your computer. Replace the placeholders with your own values.
Gemini CLI
gemini mcp add -e "CLICKHOUSE_HOST=<YOUR_CLICKHOUSE_HOST>" -e "CLICKHOUSE_USER=<YOUR_CLICKHOUSE_USER>" -e "CLICKHOUSE_PASSWORD=<YOUR_CLICKHOUSE_PASSWORD>" clickhouse uvx mcp-clickhouseThis adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients that start local servers accept this shape:
{
"mcpServers": {
"clickhouse": {
"command": "uvx",
"args": [
"mcp-clickhouse"
],
"env": {
"CLICKHOUSE_HOST": "<YOUR_CLICKHOUSE_HOST>",
"CLICKHOUSE_USER": "<YOUR_CLICKHOUSE_USER>",
"CLICKHOUSE_PASSWORD": "<YOUR_CLICKHOUSE_PASSWORD>"
}
}
}
}Zed puts servers under context_servers in its settings, with the same command, args and env fields.
Needs uv (Python) on your computer. Replace the placeholders with your own values.
listing.faq
Can I paste mcp.tc/i/clickhouse into my MCP client?
No. ClickHouse runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is uvx mcp-clickhouse.
Does ClickHouse need an API key?
Yes. It reads CLICKHOUSE_HOST, CLICKHOUSE_USER and CLICKHOUSE_PASSWORD from its environment, and CLICKHOUSE_PASSWORD is a secret. Put the value in your client's config on your own machine, never in a shared file.
Is ClickHouse a remote or a local server?
Local. Your client starts it as a process on your computer with uvx mcp-clickhouse, which needs uv (Python).
What can ClickHouse do?
You can run SQL queries on a ClickHouse cluster, read-only by default, list all databases on the cluster and list tables in a database with LIKE filters and pagination.
Which clients can use it?
Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.
Who wrote this page?
mcp.tc's robot read ClickHouse's public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
listing.em.h
listing.em.lead_local listing.em.how
listing.em.badge
[](https://mcp.tc/i/clickhouse)<a href="https://mcp.tc/i/clickhouse"><img src="https://mcp.tc/i/clickhouse/badge.svg" alt="ClickHouse on mcp.tc" height="20"></a>listing.em.badge_note
listing.em.widget
<script src="https://mcp.tc/w/clickhouse.js" async></script>listing.em.widget_note
iframe
<iframe src="https://mcp.tc/embed/clickhouse" title="ClickHouse on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>listing.em.iframe_note
listing.disclaimer_checked