Compared · postgres
19 PostgreSQL MCP servers. Which one to use.
Every PostgreSQL server we index, with whether its source is still reachable and whether we hold a screening verdict. 1 of 19 have a source repository that is no longer publicly reachable.
Scope: 19 servers, mostly mirrored from the MCP registry as of 2026-08-13. Most servers whose authors never published to the registry are absent, so treat this as close to the registry's view rather than a complete census.
| Server | Publisher | Source | Screened | Quality | Install |
|---|---|---|---|---|---|
| Postgres MCP | io.github.edelciomolina | no flag | REVIEW | 93 | npm @edelciomolina/postgres-mcp |
| PostgreSQL (hardened, read-only) | io.github.Eszetael | no flag | not screened | 90 | npm postgres-mcp-hardened |
| io.github.AINative-Studio/ainative-postgres-mcp | io.github.AINative-Studio | no flag | REVIEW | 85 | npm ainative-postgres-mcp |
| Postgres AIops | io.github.AIops-tools | no flag | REVIEW | 85 | pypi postgres-aiops |
| sw-postgres-mcp | io.github.jpka | no flag | not screened | 85 | npm sw-postgres-mcp |
| io.github.ofershap/postgres | io.github.ofershap | no flag | not screened | 85 | npm mcp-pg-server |
| PostgreSQL MCP Server | io.github.itunified-io | no flag | REVIEW | 83 | npm @itunified.io/mcp-postgres |
| io.github.arifulislamat/database-mcp-postgres | io.github.arifulislamat | no flag | REVIEW | 80 | npm @database-mcp/postgres |
| PostgreSQL MCP Server | io.github.neverinfamous | no flag | REVIEW | 77 | npm @neverinfamous/postgres-mcp |
| io.github.marcelo-ochoa/postgres | io.github.marcelo-ochoa | no flag | REVIEW | 76 | npm @marcelo-ochoa/server-postgres |
| io.github.bluwork/postgres-scout-mcp | io.github.bluwork | no flag | REVIEW | 75 | npm postgres-scout-mcp |
| PostgreSQL MCP Server | io.github.neverinfamous | no flag | REVIEW | 74 | docker docker.io/writenotenow/postgres-mcp-enhanced:v1.2.0 |
| capital.hove/read-only-local-postgres-mcp-server | capital.hove | no flag | REVIEW | 73 | npm @hovecapital/read-only-postgres-mcp-server |
| io.github.pgEdge/postgres-mcp | io.github.pgEdge | no flag | REVIEW | 72 | docker ghcr.io/pgedge/postgres-mcp:latest |
| io.github.YawLabs/postgres-mcp | io.github.YawLabs | no flag | REVIEW | 70 | npm @yawlabs/postgres-mcp |
| Postgres Secured (Aegis Zero-Trust) | io.github.Yash-0620 | no flag | not screened | 67 | not published |
| ai.waystation/postgres | ai.waystation | no flag | REVIEW | 57 | remote endpoint |
| io.github.martymarkenson/postgres-connector | io.github.martymarkenson | no flag | REVIEW | 48 | npm postgres-connector |
| io.github.infoinlet-marketplace/mcp-postgres-nl-query | io.github.infoinlet-marketplace | repo unreachable | REVIEW | 77 | npm @infoinlet/mcp-postgres-nl-query |
“Repo unreachable” means the source returned a not-found from two vantage points, which can also happen when a repository is made private or moved - see source liveness. “Screened” is the advisory verdict on the listing text, never a safety clearance; the methodology spells out what each dimension does and does not test.