PostgreSQL MCP Server vs Supabase MCP Server
Both connect Claude to a Postgres database, but from different directions: the official PostgreSQL reference server is a thin, archived reference implementation for querying any Postgres instance, while the Supabase MCP server is actively maintained and speaks to a full Supabase project — database, auth, and storage included. If you're on Supabase, the choice is easy; for a bare Postgres box, weigh the reference server's archived status against its simplicity.
GitHub data verified 2026-07-30 — objective fields only, no editorial scoring.
| PostgreSQL MCP Server Connect Claude to PostgreSQL databases for querying and schema exploration | Supabase MCP Server Full Supabase backend integration including auth, database, and storage | |
|---|---|---|
| GitHub stars | 293 | 2,843 |
| Forks | 165 | 389 |
| Open issues | 0 | 107 |
| Last commit | 2025-05-28 | 2026-07-29 |
| Maintenance status | Archived (read-only) | Actively maintained |
| License | MIT | Apache-2.0 |
| Language | TypeScript | TypeScript |
| Install | npx @modelcontextprotocol/server-postgres | — |
| Author | Anthropic | Supabase |
| Official listing | Yes | No |
| Community votes | 0 | 0 |
| Copies from directory | 0 | 0 |
GitHub statistics are measured at repository level; servers that live in a shared monorepo show that repository's stats. This comparison is generated from directory data — no sponsored placement, see the curation policy.