clickhouse-monitoring vs DBHub
clickhouse-monitoring is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.
clickhouse-monitoring is a plugin bundle for AI coding tools published by duyet. No marketplace we read lists it any more. 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-10-20. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  DBHub | |
|---|---|---|
| Community marketplace duyet/codex-claude-plugins | Removed on 2026-10-20 Version: 1.1.1 Forks (GitHub): 1 Stars (GitHub): 15 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.5.0 Downloads/month (npm): 178 238 Downloads/week (npm): 40 078 Forks (GitHub): 336 Stars (GitHub): 3 677 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 | clickhouse-monitoringno longer listed · | DBHub |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 15 | 3 677 |
| Forks (GitHub) (differs) | 1 | 336 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@bytebase/dbhub) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 17, secrets among them: 4 |
| Parts of the bundle (differs) | 1 | 3 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/duyet/codex-claude-plugins | github.com/bytebase/dbhub |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of clickhouse-monitoring
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
mcp-clickhouse io.github.infoinlet-marketplace/mcp-clickhouse
Read-only ClickHouse for AI agents — analytics queries, table inspection, sizes, health.
-
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…
-
Read-only ClickHouse monitoring and advice through the chmonitor MCP server, with pointers to its docs and codebase.
-
Browse, query, and administer your managed WaveHouse + ClickHouse projects (schema, pipes, policy).
-
SQL data health analyzer and pipeline observability evaluator.
-
Enable AI agents to manage, monitor, and query CockroachDB using natural language. Perform complex database operations, cluster management, and query execution seamlessly through…
What each says it does
clickhouse-monitoring
Agent Skill for the ClickHouse Monitor dashboard - a real-time monitoring and observability tool. Covers 45 dashboard pages including query monitoring, table management, merge operations, system metrics, security logs, and API integration.
DBHub
Token-efficient database MCP server for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, SQLite
How to run each
clickhouse-monitoring
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
DBHub As a local MCP server: npm package
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/dbhubRequires: 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 clickhouse-monitoring publish no settings it asks for, so we do not compare settings.
What it can do: clickhouse-monitoring · 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.