How is Postgres MCP Pro different from the official Postgres MCP?

The official server is read-only and exposes a small set of query/schema tools. Postgres MCP Pro adds EXPLAIN-plan analysis, an index advisor, schema-wide health checks, and a guarded write mode. Same protocol, deeper toolset.

Is the write mode safe?

Writes are gated behind an explicit safe-mode flag and require the connecting role to actually have write privileges. Pair it with a read-only Postgres role for review workflows; switch to a write role only when you genuinely want the agent to issue mutations.

Does it require Python or Docker?

Python via `uvx postgres-mcp` is the simplest path — no separate install needed if you have `uv`. A Docker image is also published if you prefer containerised deployment.

Will the index advisor change my schema automatically?

No. The advisor returns recommended indexes with cost-and-benefit estimates; applying them is left to a human-reviewed migration. Auto-applying index changes is intentionally not exposed as a tool.

Can I run it against managed Postgres (RDS, Neon, Supabase)?

Yes. The connection string format is standard `postgresql://...` so any managed provider works. For Supabase, prefer the dedicated Supabase MCP if you need RLS-aware features; use Postgres MCP Pro when raw performance work matters more than auth integration.

Postgres MCP Pro

Name: Top MCPs — curated MCP directory
Creator: Top MCPs
License: https://creativecommons.org/licenses/by/4.0/

Production-grade Postgres MCP with index advice, EXPLAIN, and health checks.

Score 74(?)Crystal DBAMIT 2.7kVerified May 6, 2026Top MCPs for Databases →

Install View on GitHub

Quick answer

What it does

Connects to a PostgreSQL database and exposes query execution, EXPLAIN plan analysis, index advice, schema health checks, and optional write tools behind an explicit safe-mode flag.

Best for

Query performance tuning
Index recommendations
Schema health audits
Guarded write workflows

Not for

Pure read-only schema exploration (use the official Postgres MCP)
Non-Postgres databases

Setup recipe

Pick your client, then follow the three steps.

Install

claude_desktop_config.jsonjson

{
  "mcpServers": {
    "postgres-mcp-pro": {
      "command": "uvx",
      "args": [
        "postgres-mcp"
      ],
      "env": {
        "DATABASE_URI": "${DATABASE_URI}"
      }
    }
  }
}

Paste under mcpServers. Fully quit and reopen Claude after editing.

CLI or .mcp.jsonshell

# export DATABASE_URI=postgresql://user:pass@localhost/db
claude mcp add postgres-mcp-pro -- uvx postgres-mcp

Run from your repo. Commit .mcp.json to share with your team.

.cursor/mcp.jsonjson

{
  "mcpServers": {
    "postgres-mcp-pro": {
      "command": "uvx",
      "args": [
        "postgres-mcp"
      ],
      "env": {
        "DATABASE_URI": "${DATABASE_URI}"
      }
    }
  }
}

Global path: ~/.cursor/mcp.json. Reload window after editing.

.vscode/mcp.jsonjsonc

{
  "servers": {
    "postgres-mcp-pro": {
      "command": "uvx",
      "args": [
        "postgres-mcp"
      ],
      "env": {
        "DATABASE_URI": "${DATABASE_URI}"
      }
    }
  }
}

VS Code uses the "servers" key (not "mcpServers").

~/.codeium/windsurf/mcp_config.jsonjson

{
  "mcpServers": {
    "postgres-mcp-pro": {
      "command": "uvx",
      "args": [
        "postgres-mcp"
      ],
      "env": {
        "DATABASE_URI": "${DATABASE_URI}"
      }
    }
  }
}

Open via Cascade → hammer icon → Configure.

cline_mcp_settings.jsonjson

{
  "mcpServers": {
    "postgres-mcp-pro": {
      "command": "uvx",
      "args": [
        "postgres-mcp"
      ],
      "env": {
        "DATABASE_URI": "${DATABASE_URI}"
      }
    }
  }
}

Open via the Cline sidebar → MCP Servers → Edit.

~/.continue/config.jsonjson

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "uvx",
          "args": [
            "postgres-mcp"
          ],
          "env": {
            "DATABASE_URI": "${DATABASE_URI}"
          }
        }
      }
    ]
  }
}

Continue uses modelContextProtocolServers with a transport block.

~/.codex/config.tomlshell

# ~/.codex/config.toml
[mcp_servers.postgres-mcp-pro]
command = "uvx"
args = [
  "postgres-mcp",
]
env = { DATABASE_URI = "${DATABASE_URI}" }

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

~/.config/zed/settings.jsonjsonc

{
  "context_servers": {
    "postgres-mcp-pro": {
      "command": {
        "path": "uvx",
        "args": [
          "postgres-mcp"
        ]
      },
      "env": {
        "DATABASE_URI": "${DATABASE_URI}"
      }
    }
  }
}

Zed calls them "context_servers". Settings live-reload on save.

ChatGPT → Apps directorynone

Postgres MCP Pro doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

2
Set required secrets
Set DATABASE_URI in your shell environment before launching your MCP client.
3
Try a minimum working prompt
Diagnose a slow report query and suggest indexes
Using Postgres MCP Pro, take this query and explain why it is slow: SELECT ... FROM ... Then run analyze_workload on the related tables and recommend the top 3 indexes that would help, with estimated cost and benefit. Do not apply any index — just propose.
Tested with: Claude Desktop, Claude Code, Cursor.

Tools & permissions

Tool	Description	Args	Side effects
`execute_sql`	Run a SQL statement; behaviour depends on safe-mode and role privileges.	sql: string	Read
`explain_query`	Return the query plan with cost estimates.	sql: string	Read
`analyze_workload`	Surface slow queries and index opportunities from pg_stat_statements.	—	Read
`recommend_indexes`	Suggest indexes for a given query or table workload, with estimated cost and benefit.	sql?: string	Read
`check_health`	Run a schema-wide health check (bloat, missing PKs, duplicate indexes, replication lag).	—	Read

Security & scope

Access scope: Read + write
Sandbox: Connects to a Postgres database via the connection string in DATABASE_URI. Write tools are guarded by a safe-mode flag — when disabled, the server only exposes read-and-EXPLAIN capabilities. Database-level role permissions are the final guard regardless of MCP-side toggles.
Gotchas: Safe-mode is a server-side flag, not a database-level constraint — pair it with a read-only DB role for defence-in-depth.
EXPLAIN ANALYZE actually executes queries to gather timing data; on production, prefer plain EXPLAIN or run against a snapshot.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.

Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.

Recommend the best MCP servers for [task: e.g. databases work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-databases

Compare Postgres MCP Pro against a real alternative. Swap the second MCP in [brackets] if you want a different match.

Compare Postgres MCP Pro MCP vs [PostgreSQL MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/postgres-mcp-pro
- top-mcps.com listing for PostgreSQL

Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.

Install the Postgres MCP Pro MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/postgres-mcp-pro (fetch https://top-mcps.com/mcp/postgres-mcp-pro.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (DATABASE_URI) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.

May 6, 2026
Refreshed install snippets and fact sheet; verified for 2026.
Apr 10, 2025
Initial directory listing.

More Databases MCPs

Other tools in the same category worth evaluating.

PostgreSQL

Official

Query and inspect PostgreSQL databases via natural language.

databasesqlpostgresqueries

3 minLow

SQLite

Local SQLite database access with full read/write support.

databasesqlitelocalstorage

2 minLow

Supabase

Full Supabase access: database, auth, storage, and edge functions.

supabasedatabasebackendpostgres

5 minLow

Compared with Postgres MCP Pro

Side-by-side breakdowns for the choices people most often weigh against this MCP.

Postgres MCP ProvsPostgreSQL Postgres MCP ProvsSupabase Postgres MCP ProvsSQLite

Exploring Top MCPs for Databases? See all Databases MCPs →