Comparison

ClickHouse vs California Code

ClickHouse is an MCP server published by ClickHouse. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, PyPI (MCP servers)). California Code is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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	California Code
Official MCP Registry	Listed Version: 0.7.0 Downloads/month (PyPI): 240 897 Downloads/week (PyPI): 61 608 Forks (GitHub): 210 Stars (GitHub): 898 Not marked · First seen 2026-10-11	Listed Version: 0.1.4 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen 2026-10-11
Docker MCP Catalog	Listed Version: sha256:51bcd33e17ad Forks (GitHub): 210 Pulls (Docker Hub): 382 348 Stars (Docker Hub): 3 Stars (GitHub): 898 Not marked · First seen 2026-10-11	Not listed
PyPI (MCP servers)	Listed Version: 0.7.0 Downloads/month (PyPI): 240 897 Downloads/week (PyPI): 61 608 Forks (GitHub): 210 Stars (GitHub): 898 Not marked · First seen 2026-10-12	Not listed

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 California Code
Fact	ClickHouse	California Code
Marketplaces that list it (differs)	3 (better)	1 (worse)
Stars (GitHub) (differs)	898 (better)	0 (worse)
Pulls (Docker Hub) (differs)	382 348	No figure on Docker Hub
Forks (GitHub) (differs)	210 (better)	0 (worse)
Last release (differs)	Not published	2026-10-23
Where it runs (differs)	On your machine (mcp-clickhouse)	Remote server (gateway.pipeworx.io/california-code/mcp)
Transport (differs)	stdio	Streamable HTTP
Tools it declares (differs)	3	Not published
Environment variables it asks for (differs)	16, secrets among them: 1	Not published
Licence (differs)	Apache-2.0	Not stated
Repository (differs)	github.com/clickhouse/mcp-clickhouse	github.com/pipeworx-io/mcp-california-code
Changes in the last 7 days (differs)	0	1
First seen	2026-10-11	2026-10-11
Endpoint at the last check (differs)	no remote endpoint we check	Responded 9 h ago

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 Official MCP Registry:

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

California Code

In its own words, on Official MCP Registry:

California Codes — the text of California statutes, by citation.

How to run each

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

California Code As a remote MCP server

Claude Code

claude mcp add --transport http california-code https://gateway.pipeworx.io/california-code/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only California Code has a remote endpoint we check. How we check endpoints

Tools each declares

Only ClickHouse has

list_databases
list_tables
run_select_query

Only California Code has

ai_visibility_check
archive_compare
archive_evidence
ask_pipeworx
ask_pipeworx_beta
ask_pipeworx_grounded
bet_research
ca_code_section
ca_codes
classify_row
company_facts
company_register_search

Show the remaining 34

compare_entities
deep_research
discover_tools
entity_profile
forget
generate_llms_txt
kalshi_weather_edge
list_subscriptions
pipeworx_feedback
pipeworx_trending
polymarket_arbitrage
polymarket_edge_tracker
polymarket_edges
polymarket_fill_risk
polymarket_kalshi_spread
prediction_calibration
recall
recent_alerts
recent_changes
release_calendar_markets
remember
research_row
resolution_audit
resolution_diff
resolve_entity
scan_competitor_ai_presence
scan_dependency
search_within
subscribe
suggest_questions
unsubscribe
updown_divergence_rate
updown_venue_compare
validate_claim

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (California Code as of 2026-10-28). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

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

What it can do: ClickHouse · What it can do: California Code · Compare two other plugins

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 2026-10-28. We publish no contact details for plugin publishers.