MCP Database Server vs WHOOP MCP
MCP Database Server is an MCP server published by Souhar-dya. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). WHOOP MCP is an MCP server published by cunicopia-dev. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.3.1 Forks (GitHub): 13 Stars (GitHub): 19 Not marked · First seen |
Listed Version: 0.1.0 Downloads/month (PyPI): 191 Downloads/week (PyPI): 19 Forks (GitHub): 1 Stars (GitHub): 0 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:9ccd629df448 Forks (GitHub): 13 Stars (GitHub): 19 Not marked · First seen |
Not listed |
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 | MCP Database Server | WHOOP MCP |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 19 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 13 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (docker.io/souhardyak/mcp-db-server:1.3.1) | On your machine (whoop-postgres-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 7 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | 4, secrets among them: 3 |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/souhar-dya/mcp-db-server | github.com/cunicopia-dev/whoop-mcp |
| Changes in the last 7 days | 0 | 0 |
| 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
MCP Database Server
MCP server for SQLite, PostgreSQL, and MySQL with natural language to SQL and direct SQL tooling.
WHOOP MCP
Sync WHOOP recovery, sleep, strain, and workouts into Postgres and query them from any MCP client.
How to run each
MCP Database Server As a local MCP server: Docker image
claude mcp add --transport stdio mcp-db-server -- docker run -i --rm docker.io/souhardyak/mcp-db-server:1.3.1
WHOOP MCP As a local MCP server: PyPI package
claude mcp add --env "WHOOP_CLIENT_ID=<YOUR_WHOOP_CLIENT_ID>" --env "WHOOP_CLIENT_SECRET=<YOUR_WHOOP_CLIENT_SECRET>" --env "WHOOP_DB_URL=<YOUR_WHOOP_DB_URL>" --env "WHOOP_REDIRECT_URI=<YOUR_WHOOP_REDIRECT_URI>" --transport stdio whoop-postgres-mcp -- uvx whoop-postgres-mcp
Requires: WHOOP_CLIENT_ID (secret), WHOOP_CLIENT_SECRET (secret), WHOOP_DB_URL (secret), WHOOP_REDIRECT_URI
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of WHOOP MCP publish no list of tools, so we do not compare tools.
Settings each asks for
Only MCP Database Server asks for
DATABASE_URL
Only WHOOP MCP asks for
WHOOP_CLIENT_ID (secret)WHOOP_CLIENT_SECRET (secret)WHOOP_DB_URL (secret)WHOOP_REDIRECT_URI
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: MCP Database Server · What it can do: WHOOP MCP · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.