Comparison

clickhouse vs ClickHouse

clickhouse is a plugin bundle for AI coding tools published by ClickHouse. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins, Claude Code: claude-plugins-community). ClickHouse is an MCP server published by ClickHouse. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-15. 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

Where each is published
Marketplace	clickhouse	ClickHouse
Claude Code: claude-plugins-official	Listed Version: 1.0.0 Forks (GitHub): 2 Stars (GitHub): 7 Not marked · First seen 2026-10-11	Not listed
Claude: knowledge-work-plugins	Listed Version: 1.0.0 Forks (GitHub): 2 Stars (GitHub): 7 Not marked · First seen 2026-10-11	Not listed
Claude Code: claude-plugins-community	Listed Version: 1.0.0 Forks (GitHub): 2 Stars (GitHub): 7 Not marked · First seen 2026-10-11	Not listed
Official MCP Registry	Not listed	Listed Version: 0.7.0 Downloads/month (PyPI): 240 897 Downloads/week (PyPI): 54 389 Forks (GitHub): 208 Stars (GitHub): 887 Not marked · First seen 2026-10-11
Docker MCP Catalog	Not listed	Listed Version: sha256:51bcd33e17ad Forks (GitHub): 208 Pulls (Docker Hub): 352 668 Stars (Docker Hub): 3 Stars (GitHub): 887 Not marked · First seen 2026-10-11

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

clickhouse vs ClickHouse
Fact	clickhouse	ClickHouse
Marketplaces that list it (differs)	3 (better)	2 (worse)
Stars (GitHub) (differs)	7 (worse)	887 (better)
Pulls (Docker Hub) (differs)	No figure on Docker Hub	352 668
Forks (GitHub) (differs)	2 (worse)	208 (better)
Last release	Not published	Not published
Where it runs (differs)	Remote server (mcp.clickhouse.cloud/mcp)	On your machine (mcp-clickhouse)
Transport (differs)	Streamable HTTP	stdio
Tools it declares (differs)	Not published	3
Environment variables it asks for (differs)	Not published	16, secrets among them: 1
Parts of the bundle (differs)	3	Not a bundle
Licence	Apache-2.0	Apache-2.0
Repository (differs)	github.com/clickhouse/clickhouse-claude-code-plugin	github.com/clickhouse/mcp-clickhouse
Changes in the last 7 days	0	0
First seen	2026-10-11	2026-10-11
Endpoint at the last check (differs)	Responded 3 days ago, requires a key	no remote endpoint we check

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

clickhouse

In its own words, on Claude Code: claude-plugins-official:

Connect Claude to your ClickHouse Cloud databases. Browse organizations, services, databases, and table schemas. Run read-only SQL queries against your data and get instant analytical answers. Monitor service backups, review billing costs, and inspect ClickPipe configurations - all through natural conversation.

ClickHouse

In its own words, on Official MCP Registry:

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

How to run each

clickhouse As a Claude Code plugin

Claude Code

/plugin install clickhouse@claude-plugins-official

ClickHouse As a local MCP server: PyPI package

Claude Code

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-clickhouse

Requires: 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.

Only clickhouse has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of clickhouse publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of clickhouse publish no settings it asks for, so we do not compare settings.

What it can do: clickhouse · What it can do: ClickHouse · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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 2026-10-15. We publish no contact details for plugin publishers.