Neon vs Dataset to Postgres, Supabase & MySQL (Database Push)
Neon is an MCP server published by neondatabase. Marketplaces we read that list it: 1 (Docker MCP Catalog). Dataset to Postgres, Supabase & MySQL (Database Push) is an MCP server published by Nero-Engine. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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 |   Neon |  Dataset to Postgres, Supabase & MySQL (Database Push) |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:fab32eb73fb0 Forks (GitHub): 130 Pulls (Docker Hub): 23 327 Stars (Docker Hub): 3 Stars (GitHub): 651 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 No figure published 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 | Neon | Dataset to Postgres, Supabase & MySQL (Database Push) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 651 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 23 327 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 130 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/neon) | Remote server (mcp.apify.com) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 19 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/neondatabase-labs/mcp-server-neon | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
MCP server for interacting with Neon Management API and databases.
Dataset to Postgres, Supabase & MySQL (Database Push)
Push rows from a dataset, file or Google Sheet into a Postgres, Supabase, Neon or MySQL table.
How to run each
Neon As a local MCP server: Docker image
claude mcp add --env "NEON_API_KEY=<YOUR_NEON_API_KEY>" --transport stdio neon -- docker run -i --rm -e NEON_API_KEY mcp/neonRequires: NEON_API_KEY (secret)
Dataset to Postgres, Supabase & MySQL (Database Push)
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Dataset to Postgres, Supabase & MySQL (Database Push) publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Dataset to Postgres, Supabase & MySQL (Database Push) publish no settings it asks for, so we do not compare settings.
What it can do: Neon · What it can do: Dataset to Postgres, Supabase & MySQL (Database Push) · 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.