Supabase

Supabase’s official MCP server goes past read-only database access — it can create and manage projects, run schema migrations, inspect and query tables, manage Auth and Storage config, and deploy Edge Functions, effectively the same surface area as the Supabase dashboard, exposed as agent tools instead.

A --read-only flag is available and worth defaulting to for anything other than a dedicated dev or staging project, since the full-access mode can genuinely alter schema and data — closer in risk profile to handing an agent a service-role key than to the read-only Postgres reference server elsewhere in this catalog.

If a project is already on Supabase for its database, this largely replaces the need for the separate PostgreSQL MCP server — it covers the same querying use case plus project- and infrastructure-level operations that server doesn’t touch.