How many PostgreSQL MCP servers are there?

15 PostgreSQL MCP servers are indexed on mcpindex as of 2026-07-25. That is what the MCP registry lists, not necessarily every one that exists.

Which PostgreSQL MCP server should I use?

Of the 15 indexed, Postgres MCP (io.github.edelciomolina/postgres-mcp) has the highest MCP Quality Score at 94/100 and no source-liveness flag. A high score means the listing is complete and current, not that the server is safe.

Are any PostgreSQL MCP servers abandoned?

1 of 15 have a source repository that is no longer publicly reachable. That can also mean the repository was made private or relocated, so it is an observation rather than a conclusion.

← Index

Compared · postgres

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

Scope: 15 servers indexed from the MCP registry as of 2026-07-25. Servers whose authors never published to the registry are not listed here, so treat this as the registry's view rather than a complete census.

Server	Publisher	Source	Screened	Quality	Install
Postgres MCP	io.github.edelciomolina	no flag	REVIEW	94	npm @edelciomolina/postgres-mcp
Postgres AIops	io.github.AIops-tools	no flag	REVIEW	85	pypi postgres-aiops
PostgreSQL MCP Server	io.github.itunified-io	no flag	REVIEW	84	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	79	npm @neverinfamous/postgres-mcp
io.github.bluwork/postgres-scout-mcp	io.github.bluwork	no flag	REVIEW	77	npm postgres-scout-mcp
io.github.marcelo-ochoa/postgres	io.github.marcelo-ochoa	no flag	REVIEW	77	npm @marcelo-ochoa/server-postgres
PostgreSQL MCP Server	io.github.neverinfamous	no flag	REVIEW	75	docker docker.io/writenotenow/postgres-mcp-enhanced:v1.2.0
capital.hove/read-only-local-postgres-mcp-server	capital.hove	no flag	REVIEW	74	npm @hovecapital/read-only-postgres-mcp-server
io.github.pgEdge/postgres-mcp	io.github.pgEdge	no flag	REVIEW	73	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	68	not published
ai.waystation/postgres	ai.waystation	no flag	REVIEW	58	remote endpoint
io.github.martymarkenson/postgres-connector	io.github.martymarkenson	no flag	REVIEW	50	npm postgres-connector
io.github.infoinlet-marketplace/mcp-postgres-nl-query	io.github.infoinlet-marketplace	repo unreachable	REVIEW	78	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.