Ext Ops Panel
Open dashboard
Comparison

infra-clickhouse vs DBHub

infra-clickhouse is a plugin bundle for AI coding tools published by ClickHouse Inc. Marketplaces we read that list it: 1 (Community GitHub marketplaces). DBHub is an MCP server published by bytebase. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-11-03. 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
Marketplaceinfra-clickhouseDBHub
Community marketplace clickhouse/agent-skills Listed
Version: 0.4.0
Forks (GitHub): 38
Stars (GitHub): 564
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.5.1
Downloads/month (npm): 133 248
Downloads/week (npm): 17 149
Forks (GitHub): 330
Stars (GitHub): 3 771
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

infra-clickhouse vs DBHub
Factinfra-clickhouseDBHub
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)564 (worse)3 771 (better)
Forks (GitHub) (differs)38 (worse)330 (better)
Last release (differs)2026-11-02 (worse)2026-11-03 (better)
Where it runs (differs)Installs as a plugin bundleOn your machine (@bytebase/dbhub)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published17, secrets among them: 4
Parts of the bundle (differs)Not published3
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/clickhouse/agent-skillsgithub.com/bytebase/dbhub
Changes in the last 7 days (differs)12
First seen2026-10-112026-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

infra-clickhouse

In its own words, on Community GitHub marketplaces:

Local and cloud workflows for running ClickHouse with clickhousectl — local development (install ClickHouse, start a server, create schemas, seed data) and ClickHouse Cloud deployment (authenticate, create a service, migrate schemas, connect an application), with a decision tree routing between them

DBHub

In its own words, on Official MCP Registry:

Token-efficient database MCP server for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, SQLite

How to run each

infra-clickhouse As a Claude Code plugin

Claude Code
/plugin marketplace add clickhouse/agent-skills
/plugin install infra-clickhouse@clickhouse-agent-skills

DBHub As a local MCP server: npm package

Claude Code
claude mcp add --env "DB_PASSWORD=<YOUR_DB_PASSWORD>" --env "DSN=<YOUR_DSN>" --env "SSH_PASSPHRASE=<YOUR_SSH_PASSPHRASE>" --env "SSH_PASSWORD=<YOUR_SSH_PASSWORD>" --transport stdio dbhub -- npx -y @bytebase/dbhub

Requires: DB_PASSWORD (secret), DSN (secret), SSH_PASSPHRASE (secret), SSH_PASSWORD (secret)

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

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

What it can do: infra-clickhouse · What it can do: DBHub · 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. 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