PostgreSQL MCP is Anthropic’s reference server for letting an agent query a Postgres database safely. Read-only by default, exposing query, list_tables, describe_table, and explain tools. The model gets enough surface to debug a slow query or write an analytics report without ever holding write privileges.
What it produces: raw query results as JSON, schema metadata for every table, and EXPLAIN ANALYZE output the model can reason about for tuning.
Best for: founders running a Supabase or Neon database who want Claude to answer “how many users signed up last week from the FR market?” without writing the SQL by hand. Also great for DBA-style work — index suggestions, slow query triage, schema drift checks.
Skip if: you need writes — by design, this server is read-only (which is correct). For full CRUD use Supabase MCP, which adds auth + storage + edge functions on top.
Setup gotchas: the server is in servers-archived — Anthropic moved active maintenance to community forks. Still works, but expect no new features. Connection string goes in your MCP config, not the prompt — never paste it where logs or git might capture it. Use a read-only role on your DB, not the service-role key.
Real-world workflow: I keep it pointed at a read-replica of my Supabase instance. Weekly: “show me the funnel from signup to first paid action over the last 30 days, grouped by acquisition channel.” It writes the SQL, runs it, formats the result. 30 seconds vs. 15 minutes of dashboard navigation.
Compatible alternatives: Supabase MCP for full Supabase platform, SQLite MCP for local dev, Redis MCP for cache layer.
Read-only is a feature, not a bug. Resist the urge to grant write.