PostgreSQL MCP

This reference server is intentionally narrow: expose a PostgreSQL database to an agent for schema discovery and read-only analysis. That boundary is useful for audits and reporting, but it is not a write-capable database operator and is not a current maintained package.

Connection / transport

stdio via NPX or Docker

Authentication

Database connection URL credentials; local process access

Use a read-only database user and configure `@modelcontextprotocol/server-postgres` with a PostgreSQL URL. The archived README's NPX example is `npx -y @modelcontextprotocol/server-postgres postgresql://localhost/mydb`.

Documented setup example. Review the source and credentials before running; this command was not executed for this article.

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

Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.

Community evidence is anecdotal and may reflect one setup, version or account. It is included for discovery and risk-sensing, not as a representative rating or independent benchmark. Verify the current official documentation before acting on a report.

Proposed workflow: answer a data question safely

Suggested evaluation, not an observed test result.

1. Create a database role limited to the reporting schema and read-only transactions.
2. Inspect the schema before writing a query.
3. Run a bounded query, cite its timestamp and have a human review the interpretation.

What to inspect: A reproducible analysis trail without database mutation. No database connection or query was executed here.

A reproducible analysis trail without database mutation. No database connection or query was executed here.

Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.