chdb-sql vs ClickHouse
chdb-sql is a plugin bundle for AI coding tools published by ClickHouse Inc. Marketplaces we read that list it: 1 (Community GitHub marketplaces). ClickHouse is an MCP server published by ClickHouse. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, PyPI (MCP servers)). As of our marketplace pass on 2026-10-26. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  chdb-sql |  ClickHouse |
|---|---|---|
| Community marketplace clickhouse/agent-skills | Listed Version: 4.1.0 Forks (GitHub): 38 Stars (GitHub): 561 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.7.0 Downloads/month (PyPI): 240 897 Downloads/week (PyPI): 61 608 Forks (GitHub): 210 Stars (GitHub): 893 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:51bcd33e17ad Forks (GitHub): 210 Pulls (Docker Hub): 376 288 Stars (Docker Hub): 3 Stars (GitHub): 893 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.7.0 Downloads/month (PyPI): 240 897 Downloads/week (PyPI): 61 608 Forks (GitHub): 210 Stars (GitHub): 893 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | chdb-sql | ClickHouse |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 561 (worse) | 893 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 376 288 |
| Forks (GitHub) (differs) | 38 (worse) | 210 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (mcp-clickhouse) |
| Transport (differs) | Not stated | stdio |
| Tools it declares (differs) | Not published | 3 |
| Environment variables it asks for (differs) | Not published | 16, secrets among them: 1 |
| Licence | Apache-2.0 | Apache-2.0 |
| Repository (differs) | github.com/clickhouse/agent-skills | github.com/clickhouse/mcp-clickhouse |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
chdb-sql
Embedded ClickHouse SQL engine for Python via chDB — run analytical SQL on parquet/csv/json files, URLs, S3, and remote databases (Postgres, MySQL, MongoDB, ClickHouse Cloud, Iceberg, Delta Lake) with Session for stateful pipelines, parametrized queries, UDFs, and cross-source joins
ClickHouse
Official ClickHouse MCP server for querying and exploring ClickHouse clusters and chDB.
How to run each
chdb-sql As a Claude Code plugin
/plugin marketplace add clickhouse/agent-skills
/plugin install chdb-sql@clickhouse-agent-skillsClickHouse As a local MCP server: PyPI package
claude mcp add --env "CLICKHOUSE_HOST=<YOUR_CLICKHOUSE_HOST>" --env "CLICKHOUSE_PASSWORD=<YOUR_CLICKHOUSE_PASSWORD>" --env "CLICKHOUSE_USER=<YOUR_CLICKHOUSE_USER>" --transport stdio mcp-clickhouse -- uvx mcp-clickhouseRequires: CLICKHOUSE_HOST, CLICKHOUSE_PASSWORD (secret), CLICKHOUSE_USER
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of chdb-sql publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of chdb-sql publish no settings it asks for, so we do not compare settings.
What it can do: chdb-sql · What it can do: ClickHouse · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.