Ext Ops Panel
Open dashboard
Comparison

cedardb vs DBHub

cedardb is a plugin bundle for AI coding tools published by CedarDB. 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-10-14. 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
MarketplacecedardbDBHub
Community marketplace cedardb/claude-plugin Listed
Version: 1.0.0
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.5.0
Downloads/month (npm): 171 965
Downloads/week (npm): 38 108
Forks (GitHub): 320
Stars (GitHub): 3 645
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

cedardb vs DBHub
FactcedardbDBHub
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub3 645
Forks (GitHub) (differs)No figure on GitHub320
Last releaseNot publishedNot published
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
Hooks it runs (differs)1Not published
Parts of the bundle (differs)73
Licence (differs)Not statedMIT
Repository (differs)github.com/cedardb/claude-plugingithub.com/bytebase/dbhub
Changes in the last 7 days22
First seen (differs)2026-10-142026-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

cedardb

In its own words, on Community GitHub marketplaces:

Deploy, query, and visualize with the help of CedarDB directly from Claude Code.

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

cedardb As a Claude Code plugin

Claude Code
/plugin marketplace add cedardb/claude-plugin
/plugin install cedardb@cedardb

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 cedardb publish no settings it asks for, so we do not compare settings.

What it can do: cedardb · 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