Supabase vs Hetzner DNS
Supabase is a plugin bundle for AI coding tools published by Supabase. Marketplaces we read that list it: 1 (Codex: openai-curated (openai/plugins)). Hetzner DNS is an MCP server published by ni-c. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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 |  Hetzner DNS | |
|---|---|---|
| Codex: openai-curated (openai/plugins) | Listed Version: 1.0.0 Forks (GitHub): 970 Stars (GitHub): 7 455 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.6.0 Downloads/month (npm): 293 Downloads/week (npm): 52 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 | Supabase | Hetzner DNS |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 7 455 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 970 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.supabase.com/mcp) | On your machine (hetzner-dns-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 5, secrets among them: 1 |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/openai/plugins | github.com/ni-c/hetzner-dns-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago, requires a key | no remote endpoint we check |
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
Supabase
Manage Supabase projects directly through ChatGPT. Execute SQL queries on PostgreSQL databases, design and modify table schemas, deploy serverless edge functions, and configure user authentication. Access real-time logs for debugging, create and apply database migrations, and manage development branches through natural language.
Hetzner DNS
Manage DNS zones and records (zonefiles, RRSets, TTL, protection) via the Hetzner Cloud API
How to run each
Supabase As a Codex plugin
codex plugin marketplace add openai/pluginsHetzner DNS As a local MCP server: npm package
claude mcp add --env "HETZNER_API_TOKEN=<YOUR_HETZNER_API_TOKEN>" --transport stdio hetzner-dns-mcp -- npx -y hetzner-dns-mcpRequires: HETZNER_API_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Supabase has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Supabase publish no settings it asks for, so we do not compare settings.
What it can do: Supabase · What it can do: Hetzner DNS · Compare two other plugins
Data comes from the public marketplace file https://github.com/openai/plugins/blob/HEAD/.agents/plugins/marketplace.json. 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.