Ext Ops Panel
Open dashboard
Comparison

Neon vs DBHub

Neon is an MCP server published by neondatabase. Marketplaces we read that list it: 1 (Docker MCP Catalog). DBHub is an MCP server published by bytebase. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
MarketplaceNeonDBHub
Docker MCP Catalog Listed
Version: sha256:fab32eb73fb0
Forks (GitHub): 130
Pulls (Docker Hub): 23 267
Stars (Docker Hub): 3
Stars (GitHub): 651
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 635
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

Neon vs DBHub
FactNeonDBHub
Marketplaces that list it11
Stars (GitHub) (differs)651 (worse)3 635 (better)
Pulls (Docker Hub) (differs)23 267No figure on Docker Hub
Forks (GitHub) (differs)130 (worse)318 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/neon)On your machine (@bytebase/dbhub)
Transportstdiostdio
Tools it declares (differs)19Not published
Environment variables it asks for (differs)1, secrets among them: 117, secrets among them: 4
Licence (differs)MITNot stated
Repository (differs)github.com/neondatabase-labs/mcp-server-neongithub.com/bytebase/dbhub
Changes in the last 7 days00
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

Neon

In its own words, on Docker MCP Catalog:

MCP server for interacting with Neon Management API and databases.

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

Neon As a local MCP server: Docker image

Claude Code
claude mcp add --env "NEON_API_KEY=<YOUR_NEON_API_KEY>" --transport stdio neon -- docker run -i --rm -e NEON_API_KEY mcp/neon

Requires: NEON_API_KEY (secret)

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

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

Settings each asks for

Only Neon asks for

  • NEON_API_KEY (secret)

Only DBHub asks for

  • DB_HOST
  • DB_NAME
  • DB_PASSWORD (secret)
  • DB_PORT
  • DB_TYPE
  • DB_USER
  • DSN (secret)
  • ID
  • PORT
  • SSH_AUTH_SOCK
  • SSH_HOST
  • SSH_KEY
Show the remaining 5
  • 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: Neon · What it can do: DBHub · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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