Postgres MCP Pro

Name: Postgres MCP Pro
Availability: InStock
Author: Kata Team

Read/write Postgres plus health checks, index tuning, and EXPLAIN analysis.

Software Development Database & Data Engineering @katateam

Before you connect: what this server would do

A preview derived from this server’s definition — not a live run. Nothing runs and no key is sent until you connect. You run this server on your own machine — FindAgent never runs it.

Tools it can use (5)

list_schemas
List schemas in the database.
execute_sql
Run a SQL statement (subject to the access mode).
explain_query
EXPLAIN a query with hypothetical-index simulation.
analyze_db_health
Run database-health diagnostics.
analyze_workload_indexes
Recommend indexes for the workload.

Credentials it will ask for (1)

PostgreSQL Connection String

What FindAgent checked

It passed an automated security scan and a human review before it was published here.
Your client talks to this server directly, so FindAgent’s run-time protections — the secret and prompt-injection scan on every result, the credential-to-host binding, the approval gates — do not apply to what you send or receive here.

How FindAgent keeps servers safe

Run locally

This MCP server runs on your own machine — FindAgent only points you at it. Run the command below, then add it to your MCP client. Nothing is hosted or proxied on our side.

terminal

uvx postgres-mcp --access-mode=unrestricted

Add it to your MCP client

Paste this into your client config (e.g. claude_desktop_config.json or a Cursor mcp.json), then restart the client.

mcp client config

{
  "mcpServers": {
    "postgres-mcp-pro": {
      "command": "uvx",
      "args": [
        "postgres-mcp",
        "--access-mode=unrestricted"
      ]
    }
  }
}

View the source repository