Mmcp.market

Head to head

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

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

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
DB Accessio.github.Rheopyrin/db-access-mcp
A
No reviews yet

MCP server for Postgres/MySQL/Redshift/SQL Server over SSH/SSM tunnels with secret providers.

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 DB Access (92/100 against 67). Dataset to Postgres, Supabase & MySQL (Database Push) is hosted and callable through the gateway; DB Access runs on your own machine. DB Access has noticeably more public adoption.

 Dataset to Postgres, Supabase & MySQL (Database Push)DB Access
User ratingNo reviews yetNo reviews yet
Safety gradeC67/100A92/100
AdoptionNewGrowing
GitHub stars–0
Downloads / week–53
Runs whereHosted (remote)Your machine (local)
Gateway-readyYesNo
Tools——
Write actions——
Price per callFreeFree
Licence—MIT
Last release—2026-09-07
CategoryDatabasesDatabases

Other comparisons

Dataset to Postgres, Supabase & MySQL (Database Push) vs NeonDataset to Postgres, Supabase & MySQL (Database Push) vs PostgreSQLDataset to Postgres, Supabase & MySQL (Database Push) vs DBHubDataset to Postgres, Supabase & MySQL (Database Push) vs Magic CloudDataset to Postgres, Supabase & MySQL (Database Push) vs Microsoft Access DatabaseAll Databases servers