# There is no official Postgres MCP server. I compared the 37 that do exist.

> Source: <https://dev.to/serverdex/there-is-no-official-postgres-mcp-server-i-compared-the-37-that-do-exist-ngl>
> Published: 2026-11-20 15:35:01+00:00

**Recommendation:** When choosing a Postgres MCP server, prefer a read-only, recently pushed, permissively licensed one with a dozen focused tools over a 203-tool server that inflates every turn's context.
More in the playbook "Designing agent systems": <https://wpnews.pro/playbooks/agent-architecture>

If you want an AI agent to talk to PostgreSQL, you open your client, go looking for "the Postgres MCP server", and hit the first surprise: there isn't one. Not an official one, anyway.

I run [Serverdex](https://serverdex.io/for/postgres), a directory synced daily from the official Model Context Protocol registry. As of 20 November 2026 the index holds **37 MCP servers** whose name carries "Postgres". **Zero** of them are published by PostgreSQL or by a hosted-Postgres vendor. All 37 are community projects. So the real question is not "which is the official one" but "which of 37 community servers do I trust with my database".

Here is what the data says, and how I would pick.

Three numbers set the scene (live check, 20 Nov 2026):

That last number is the one people miss. Almost every Postgres MCP server is a **local, stdio** server: it runs on your machine, next to your client, and talks to your database over your own connection. Only two in the whole list are hosted endpoints you could point a URL at, and both of those still want something before they do real work (one is paid-per-call, one needs a sign-in). If you were hoping to add a remote URL and be done, Postgres is not that kind of category yet.

On the comparison table most rows read "Local / not checked" under live status. That is not a server being down. A stdio server has no public endpoint to call, so there is nothing to health-check from the outside — and for a database tool, local is usually what you want. Your credentials and your rows never leave your machine. Keep that in mind when a hosted alternative asks for a connection string: you are handing it the keys.

With no official server and 37 community ones, the listing is the filter. Four signals, in order:

**1. Is it read-only?** The most repeated phrase in the good entries is "read-only". Servers like the Vericto proxy check every statement before it runs; others are "read-only by default, row caps, timeouts, secrets never logged". For an agent that writes SQL you have not reviewed, read-only is the difference between a bad query and a dropped table.

**2. Is it still maintained?** The table shows last push per server. Several top entries were pushed in November 2026; a couple of popular-looking ones have not moved since 2025. An MCP server that has not been touched in a year is a server that has not kept up with the protocol's transport and auth changes.

**3. How many tools does it expose?** Two of the listed servers ship **63** and **203** tools respectively. That is not obviously good. Every tool definition is sent to the model on every turn, so a 203-tool server can cost thousands of tokens of context before you ask a single question. A focused server with a dozen well-named tools is often the better agent citizen.

**4. What is the licence?** The field is mixed: the PostgreSQL licence, Apache-2.0, MIT, and a few AGPL-3.0. If you are embedding one in a commercial product, AGPL is a decision, not a detail.

By stars, most-starred first (all community, 20 Nov 2026):

`server-postgres`. If your old config broke when that server was retired, this is the straight swap.
Stars are popularity, not correctness — but combined with "read-only", a recent push, and a licence you can live with, they are a reasonable first cut. The full table with every server, its stars, last push, live status and licence is on the page this post is drawn from.

Once you have picked a server, the config is the same shape you already know. Each server's page on Serverdex carries the exact package name and environment variables from the registry, one-click install for Cursor and VS Code, and the one-line command for Claude Code and Codex. The paths and config shapes differ per client — [Claude Code](https://serverdex.io/for-client/claude-code), [Cursor](https://serverdex.io/for-client/cursor), [VS Code](https://serverdex.io/for-client/vs-code) and the rest each read their own file in their own format — and for anything bespoke the [config generator](https://serverdex.io/mcp-config-generator) writes it.

One Postgres-specific tip: put the connection string in an environment variable, not inline in `args`, and start the server read-only until you trust it.

The registry grows daily, and "official" could change the day PostgreSQL or a hosted vendor publishes one. Until then it is 37 community servers, and the choice is yours to make on the evidence. The current, daily-rebuilt comparison — counts, the full table, and the FAQ — is at **[serverdex.io/for/postgres](https://serverdex.io/for/postgres)**. If you want a different database, the same breakdown exists for the whole [Databases category](https://serverdex.io/best-mcp-servers/databases), and the [remote servers list](https://serverdex.io/remote) shows every hosted MCP server answering right now.
