PostgreSQL MCP server

Read-only SQL, enforced by the connector rather than promised in a description.

Connect PostgreSQL All connectors

Tools: 3
Read-only: 3
Write: 0; Off by default
Destructive: 0; Flagged distinctly

What it does

PostgreSQL through an assistant

Point a connection at a PostgreSQL database and an assistant can list your tables, inspect columns and relationships, and answer questions with real SELECT queries. Read-only is structural here: there is no write tool to enable, so no permission slip can turn this into something that changes your data.

Run SELECT queries against your own database
List tables across your schemas
Describe columns, types and relationships before querying
No write tools exist at all -- nothing to switch on by mistake

Ask your assistant

What people actually ask

Real questions, answered from live PostgreSQL data.

“What tables are in this database, and how do orders and customers relate?”

postgres_list_tablespostgres_describe_table

“How many signups did we get per day over the last 30 days?”

postgres_run_readonly_query

“Which columns on the users table are nullable, and what are their types?”

postgres_describe_table

Tool catalogue

3 PostgreSQL tools

Grouped by what they touch. Every tool is individually toggleable — you expose only what you want.

All tools

3 tools3 read-only · 0 write

Showing 3 of 3 tools

postgres_describe_table
Read-only
Get column definitions and metadata for a specific table.
postgres_list_tables
Read-only
List all tables in the connected PostgreSQL database.
postgres_run_readonly_query
Read-only
Execute a read-only SELECT query against the connected PostgreSQL database. Only SELECT statements are allowed.

Every tool name and description, machine-readable: /llms-full.txt

Access & safety

You decide what it can touch

The same model applies to every connector, and it defaults closed.

Your own credential

You supply your own PostgreSQL key, scoped however you like on their side. It is encrypted with AES-256-GCM and never returned by any API response or tool call.

Writes off by default

A new connection switches on a read-oriented default set only. Every write tool must be enabled deliberately before any client can call it.

Roles enforced server-side

READ, WRITE and ADMIN gate tool invocation on the server, not just in the UI. A READ member's token is refused any write tool.

Setup

Connect PostgreSQL in minutes

No infrastructure to run. Copy one URL and one token into your client.

1Create a free workspace and connect PostgreSQL.
2Choose which tools to expose — writes stay off until you enable them.
3Copy your MCP endpoint URL and bearer token.
4Paste them into Claude, Cursor, or any MCP client.

claude_desktop_config.json

{
  "mcpServers": {
    "serve-mcp": {
      "url": "https://servemcp.com/api/mcp/your-workspace",
      "transport": "http",
      "headers": {
        "Authorization": "Bearer smcp_..."
      }
    }
  }
}