Ext Ops Panel
Open dashboard
Comparison

DBHub vs io.github.yzonur/sap-adt-mcp

DBHub is an MCP server published by bytebase. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). io.github.yzonur/sap-adt-mcp is an MCP server published by yzonur. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
MarketplaceDBHubio.github.yzonur/sap-adt-mcp
Official MCP Registry Listed
Version: 1.5.0
Downloads/month (npm): 178 238
Downloads/week (npm): 40 078
Forks (GitHub): 322
Stars (GitHub): 3 705
Not marked · First seen
Listed
Version: 0.8.57
Downloads/month (npm): 420
Downloads/week (npm): 55
Forks (GitHub): 4
Stars (GitHub): 20
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

DBHub vs io.github.yzonur/sap-adt-mcp
FactDBHubio.github.yzonur/sap-adt-mcp
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)3 705 (better)20 (worse)
Forks (GitHub) (differs)322 (better)4 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@bytebase/dbhub)On your machine (sap-adt-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)17, secrets among them: 41, secrets among them: 0
Parts of the bundle (differs)3Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/bytebase/dbhubgithub.com/yzonur/sap-adt-mcp
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

DBHub

In its own words, on Official MCP Registry:

Token-efficient database MCP server for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, SQLite

io.github.yzonur/sap-adt-mcp

In its own words, on Official MCP Registry:

Give Claude live access to SAP ABAP via ADT: read, search, check, test, and edit objects.

How to run each

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)

io.github.yzonur/sap-adt-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio sap-adt-mcp -- npx -y sap-adt-mcp

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_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

Only io.github.yzonur/sap-adt-mcp asks for

  • SAP_ADT_MCP_CONFIG

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

What it can do: DBHub · What it can do: io.github.yzonur/sap-adt-mcp · 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.

Where the data comes from: how the catalog is built