DBHub vs PostgreSQL Performance (read-only)
DBHub is an MCP server published by bytebase. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). PostgreSQL Performance (read-only) is an MCP server published by gouranshul. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
| Marketplace |  DBHub |  PostgreSQL Performance (read-only) |
|---|---|---|
| Official MCP Registry | 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 |
Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | DBHub | PostgreSQL Performance (read-only) |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 3 677 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 336 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@bytebase/dbhub) | On your machine (ghcr.io/gouranshul/pg-perf-mcp:0.1.0) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 17, secrets among them: 4 | 4, secrets among them: 2 |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/bytebase/dbhub | github.com/gouranshul/pg-perf-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-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
DBHub
Token-efficient database MCP server for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, SQLite
PostgreSQL Performance (read-only)
Read-only PostgreSQL performance diagnostics: slow queries, EXPLAIN, index advice, locks, functions
How to run each
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)
PostgreSQL Performance (read-only)
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: MCP_API_KEY (secret), PGPERF_DB_PASSWORD (secret), PGPERF_DB_URL, PGPERF_DB_USER
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 DBHub asks for
DBHUB_DSNDB_HOSTDB_NAMEDB_PASSWORD (secret)DB_PORTDB_TYPEDB_USERDSN (secret)IDPORTSSH_AUTH_SOCKSSH_HOST
Show the remaining 6
SSH_KEYSSH_PASSPHRASE (secret)SSH_PASSWORD (secret)SSH_PORTSSH_USERTRANSPORT
Only PostgreSQL Performance (read-only) asks for
MCP_API_KEY (secret)PGPERF_DB_PASSWORD (secret)PGPERF_DB_URLPGPERF_DB_USER
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: DBHub · What it can do: PostgreSQL Performance (read-only) · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.