Supabase vs Neon
Both are vendor-run remote servers for hosted Postgres with OAuth sign-in. Supabase's documented URL supports project scoping and read-only mode; Neon documents read and write scopes and branch tools.
| Supabase | Neon | |
|---|---|---|
| Category | Data & Search | Data & Search |
| Status | Official · Supabase | Official · Neon |
| Transport | Remote (HTTP) | Remote (HTTP) |
| Auth method | OAuth (remote server) | OAuth (remote) or Neon API key |
| Scopes / permissions | Not documented | read, write |
| Tools listed | 4 | 8 |
| In Config Builder | Yes | Yes |
| Last verified | Oct 15, 2026 | Oct 15, 2026 |
| Summary | Connect agents to Supabase projects: databases, migrations, edge functions and docs. | Manage Neon serverless Postgres projects, branches and SQL in natural language. |
| Key tools |
|
|
Supabase setup
{
"mcpServers": {
"supabase": {
"url": "https://mcp.supabase.com/mcp?project_ref=<project-ref>&read_only=true"
}
}
}Neon setup
{
"mcpServers": {
"neon": {
"url": "https://mcp.neon.tech/mcp"
}
}
}Built from the verified data on each spec sheet. Check the official pages before relying on details.