Mmcp.market

Head to head

PostgreSQL vs Dataset to Postgres, Supabase & MySQL (Database Push)

Same numbers we show everywhere else, lined up. Ratings come from users, the grade comes from our scanner, adoption comes from public registries.

PostgreSQLio.github.antonorlov/mcp-postgres-server
B
No reviews yet

MCP server for PostgreSQL: local, Docker, RDS, Neon, Supabase, or behind an SSH bastion.

Full listing
Dataset to Postgres, Supabase & MySQL (Database Push)io.github.Nero-Engine/dataset-to-database
C
No reviews yet

Push rows from a dataset, file or Google Sheet into a Postgres, Supabase, Neon or MySQL table.

Full listing

The short version

Neither has been reviewed yet, so the comparison rests on the scan and the public usage numbers. The safety scan favours PostgreSQL (83/100 against 67). Dataset to Postgres, Supabase & MySQL (Database Push) is hosted and callable through the gateway; PostgreSQL runs on your own machine. PostgreSQL has noticeably more public adoption.

 PostgreSQLDataset to Postgres, Supabase & MySQL (Database Push)
User ratingNo reviews yetNo reviews yet
Safety gradeB83/100C67/100
AdoptionEstablishedNew
GitHub stars22
Downloads / week2.9k
Runs whereYour machine (local)Hosted (remote)
Gateway-readyNoYes
Tools6
Write actions1
Price per callFreeFree
LicenceMIT
Last release2026-09-16
CategoryDatabasesDatabases

Other comparisons