PostgreSQL MCP Server

What it does

• Single `query` tool executed inside a READ ONLY transaction — the model literally cannot write
• Per-table schema resources (postgres://<host>/<table>/schema) discovered from database metadata
• Runs via npx `@modelcontextprotocol/server-postgres` or docker `mcp/postgres`

When to use it

The minimal, safest Postgres bridge when all you need is 'let Claude inspect my schema and run SELECTs'. For index tuning and EXPLAIN analysis use Postgres MCP Pro instead.

Getting started

Add to .mcp.json under mcpServers.postgres:

{
  "command": "npx",
  "args": ["-y", "@modelcontextprotocol/server-postgres", "postgresql://localhost/mydb"]
}

Docker + host DB: use host.docker.internal in the URL on macOS.

Things to know

The upstream repo moved to modelcontextprotocol/servers-archived — the npm package still works but gets no updates. The connection URL carries credentials in plaintext config; use a least-privilege read-only role.