Ext Ops Panel
Open dashboard
Comparison

DBHawk vs DBHub

DBHawk is a plugin bundle for AI coding tools published by Datasparc. 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
MarketplaceDBHawkDBHub
Community marketplace datasparc/dbhawk-mcp-plugin Listed
Version: 0.4.1
Forks (GitHub): 0
Stars (GitHub): 0
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): 318
Stars (GitHub): 3 639
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

DBHawk vs DBHub
FactDBHawkDBHub
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)3 639 (better)
Forks (GitHub) (differs)0 (worse)318 (better)
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)3, secrets among them: 117, secrets among them: 4
Parts of the bundle (differs)13
Licence (differs)Not statedMIT
Repository (differs)github.com/datasparc/dbhawk-mcp-plugingithub.com/bytebase/dbhub
Changes in the last 7 days22
First seen (differs)2026-10-132026-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

DBHawk

In its own words, on Community GitHub marketplaces:

Read-only DBHawk datasource exploration + HawkAI over the /api/v2/mcp API.

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

DBHawk As a Claude Code plugin

Claude Code
/plugin marketplace add datasparc/dbhawk-mcp-plugin
/plugin install dbhawk@dbhawk-marketplace

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

Only DBHawk asks for

  • DBHAWK_BASE_URL
  • DBHAWK_DEFAULT_DATASOURCE
  • DBHAWK_TOKEN (secret)

Only DBHub asks for

  • DBHUB_DSN
  • DB_HOST
  • DB_NAME
  • DB_PASSWORD (secret)
  • DB_PORT
  • DB_TYPE
  • DB_USER
  • DSN (secret)
  • ID
  • PORT
  • SSH_AUTH_SOCK
  • SSH_HOST
Show the remaining 6
  • SSH_KEY
  • SSH_PASSPHRASE (secret)
  • SSH_PASSWORD (secret)
  • SSH_PORT
  • SSH_USER
  • TRANSPORT

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

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