Ext Ops Panel
Open dashboard
Comparison

Metabase vs hypequery ClickHouse

Metabase is an MCP server published by easecloudio. Marketplaces we read that list it: 2 (Docker MCP Catalog, npm registry (MCP servers)). hypequery ClickHouse is an MCP server published by hypequery. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-10. 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
MarketplaceMetabasehypequery ClickHouse
Docker MCP Catalog Listed
Version: sha256:02e633ae77a1
Forks (GitHub): 24
Pulls (Docker Hub): 52 950
Stars (Docker Hub): 3
Stars (GitHub): 83
Not marked · First seen
Not listed
npm registry (MCP servers) Listed
Version: 1.3.0
Downloads/month (npm): 3 272
Downloads/week (npm): 1 313
Forks (GitHub): 24
Stars (GitHub): 83
Not marked · First seen
Listed
Version: 0.12.0
Downloads/month (npm): 28 331
Downloads/week (npm): 9 822
Forks (GitHub): 8
Stars (GitHub): 104
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 0.12.0
No figure published
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

Metabase vs hypequery ClickHouse
FactMetabasehypequery ClickHouse
Marketplaces that list it22
Stars (GitHub) (differs)83 (worse)104 (better)
Pulls (Docker Hub) (differs)52 950No figure on Docker Hub
Forks (GitHub) (differs)24 (better)8 (worse)
Last release (differs)Not published2026-11-10
Where it runs (differs)On your machine (mcp/metabase)On your machine (@hypequery/mcp)
Transportstdiostdio
Tools it declares (differs)28Not published
Environment variables it asks for (differs)4, secrets among them: 2Not published
Licence (differs)MITApache-2.0
Repository (differs)github.com/easecloudio/mcp-metabase-servergithub.com/hypequery/hypequery
Changes in the last 7 days (differs)05
First seen (differs)2026-10-112026-10-12

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

Metabase

In its own words, on Docker MCP Catalog:

A comprehensive MCP server for Metabase with 70+ tools.

hypequery ClickHouse

In its own words, on Official MCP Registry:

Governed ClickHouse analytics for agents: named datasets and metrics as tools, never raw SQL.

How to run each

Metabase As a local MCP server: Docker image

Claude Code
claude mcp add --env "METABASE_API_KEY=<YOUR_METABASE_API_KEY>" --env "METABASE_PASSWORD=<YOUR_METABASE_PASSWORD>" --transport stdio metabase -- docker run -i --rm -e METABASE_API_KEY -e METABASE_PASSWORD mcp/metabase

Requires: METABASE_API_KEY (secret), METABASE_PASSWORD (secret)

hypequery ClickHouse As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio hypequery -- npx -y @hypequery/mcp --config "<YOUR_CONFIG>"

Requires: --config

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

Tools each declares

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

Settings each asks for

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

What it can do: Metabase · What it can do: hypequery ClickHouse · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the public npm registry (registry.npmjs.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built