← Index
Compared · postgres

38 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. 2 of 38 have a source repository that is no longer publicly reachable.

Scope: 38 servers, mostly mirrored from the MCP registry as of 2026-10-23. 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.

ServerPublisherSourceScreenedQualityInstall
PostgreSQL MCP Serverio.github.YawLabsno flagREVIEW90npm @yawlabs/postgres-mcp
Postgres (read-only)io.github.contextflono flagREVIEW90npm @contextflo/postgres-mcp
Sezzlee PostgreSQLio.github.sezzleeno flagREVIEW90npm @sezzlee/postgres-mcp
PostgreSQL (hardened, read-only)io.github.Eszetaelno flagREVIEW89npm postgres-mcp-hardened
PostgreSQLio.github.antonorlovno flagREVIEW89npm mcp-postgres-server
Postgres URL Shapeio.github.sadri-dridino flagREVIEW89remote endpoint
Postgres MCPio.github.edelciomolinano flagREVIEW87npm @edelciomolina/postgres-mcp
Kaiva Postgres MCPai.kaivno flagREVIEW85npm @kaiva/postgres-mcp
Postgres AIopsio.github.AIops-toolsno flagREVIEW85pypi postgres-aiops
WHOOP MCPio.github.cunicopia-devno flagREVIEW84pypi whoop-postgres-mcp
sw-postgres-mcpio.github.jpkano flagREVIEW82npm sw-postgres-mcp
io.github.ofershap/postgresio.github.ofershapno flagREVIEW82npm mcp-pg-server
io.github.AINative-Studio/ainative-postgres-mcpio.github.AINative-Studiono flagREVIEW81npm ainative-postgres-mcp
io.github.arifulislamat/database-mcp-postgresio.github.arifulislamatno flagREVIEW80npm @database-mcp/postgres
ai.getvda/rabbitmq-elasticsearch-postgres-stack-generator-elasticsearch-elasticsearchai.getvdano flagREVIEW79remote endpoint
ai.getvda/rabbitmq-elasticsearch-postgres-stack-generator-mongoai.getvdano flagREVIEW79remote endpoint
io.github.sparta2025/postgres-mcpio.github.sparta2025no flagREVIEW78pypi postgres-mcp-pro
ai.getvda/kafka-and-postgres-monitoring-stackai.getvdano flagREVIEW74remote endpoint
ai.getvda/minio-postgres-redis-stack-generatorai.getvdano flagREVIEW74remote endpoint
ai.getvda/postgres-grafana-stack-generatorai.getvdano flagREVIEW74remote endpoint
ai.getvda/postgres-kafka-prometheus-stack-generatorai.getvdano flagREVIEW74remote endpoint
ai.getvda/postgres-kafka-stack-generatorai.getvdano flagREVIEW74remote endpoint
ai.getvda/postgres-minio-stack-generatorai.getvdano flagREVIEW74remote endpoint
ai.getvda/postgres-prometheus-stack-generatorai.getvdano flagREVIEW74remote endpoint
ai.getvda/postgres-redis-compose-generatorai.getvdano flagREVIEW74remote endpoint
ai.getvda/rabbitmq-postgres-mongodb-stack-generatorai.getvdano flagREVIEW74remote endpoint
ai.getvda/redis-minio-postgres-stack-generatorai.getvdano flagREVIEW74remote endpoint
PostgreSQL MCP Serverio.github.neverinfamousno flagREVIEW72npm @neverinfamous/postgres-mcp
io.github.bluwork/postgres-scout-mcpio.github.bluworkno flagREVIEW70npm postgres-scout-mcp
io.github.marcelo-ochoa/postgresio.github.marcelo-ochoano flagREVIEW70npm @marcelo-ochoa/server-postgres
PostgreSQL MCP Serverio.github.neverinfamousno flagREVIEW68docker docker.io/writenotenow/postgres-mcp-enhanced:v1.2.0
capital.hove/read-only-local-postgres-mcp-servercapital.hoveno flagREVIEW67npm @hovecapital/read-only-postgres-mcp-server
io.github.pgEdge/postgres-mcpio.github.pgEdgeno flagREVIEW66docker ghcr.io/pgedge/postgres-mcp:latest
Postgres Secured (Aegis Zero-Trust)io.github.Yash-0620no flagnot screened61not published
ai.waystation/postgresai.waystationno flagREVIEW55remote endpoint
io.github.martymarkenson/postgres-connectorio.github.martymarkensonno flagREVIEW45npm postgres-connector
PostgreSQL MCP Serverio.github.itunified-iorepo unreachableREVIEW78npm @itunified.io/mcp-postgres
io.github.infoinlet-marketplace/mcp-postgres-nl-queryio.github.infoinlet-marketplacerepo unreachableREVIEW71npm @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.