1. Home
  2. Postgres MCP Pro
  3. Postgres MCP Pro for VS Code: Setup & Config

Data as of

Postgres MCP Pro for VS Code: Setup & Config

Give VS Code PostgreSQL schema access, SQL execution, health checks, and performance analysis.

Postgres MCP Pro VS Code configuration

  1. Choose VS Code configuration scope

    For Postgres MCP Pro, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

  2. Add Postgres MCP Pro to VS Code

    Use the postgres-mcp entry below in servers. Keep Postgres MCP Pro's documented stdio connection fields and your other VS Code entries.

  3. Check Postgres MCP Pro in VS Code

    Postgres MCP Pro: Start in VS Code’s MCP controls; inspect output and trust prompts.

Config file · Workspace: .vscode/mcp.json

JSON
{
  "servers": {
    "postgres-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "postgres-mcp",
        "--access-mode=restricted"
      ],
      "env": {
        "DATABASE_URI": "<PostgreSQL connection URI with your database credentials>"
      }
    }
  }
}

Postgres MCP Pro in VS Code: stdio checks

  • Make uvx postgres-mcp (from uv, for Python tools) available in the workspace, container, or remote environment hosting Postgres MCP Pro. Start through VS Code's MCP controls; inspect output and trust prompts.
  • For Postgres MCP Pro, keep DATABASE_URI out of version control; VS Code documents input variables and secret handling.
  • Postgres MCP Pro uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
Tools
list_schemas, list_objects, get_object_details

Postgres MCP Pro — details. VS Code guide

Frequently asked questions

For Postgres MCP Pro, edit workspace .vscode/mcp.json. VS Code requires servers rather than mcpServers; preserve the displayed type on each entry.

VS Code's postgres-mcp example uses stdio.

Postgres MCP Pro's VS Code configuration invokes uvx postgres-mcp (from uv, for Python tools).

VS Code's Postgres MCP Pro example references DATABASE_URI. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.

Postgres MCP Pro's stored list contains 9 tools, including list_schemas, list_objects, get_object_details. Compare those names with VS Code's connected tool list; the stored list is not a live check.