PostgreSQL MCP Server

io.github.musaddiq-devPublished by GitHub account musaddiq-devv0.1.2Updated Oct 24, 2026

Python MCP server for PostgreSQL database inspection and querying

VerifiedSTDIODesktop onlyDatabasesData & Analytics

Overview

AI-generated overview

A local Python MCP server that lets an assistant inspect and query a PostgreSQL database: list tables, read schemas, run bounded read-only SQL and explain plans

What you can do
List tables and describe table columns and metadata, plus a database summary with version and table count and a search of SQL routines and functions. Run bounded read-only SQL in a read-only transaction, explain query plans, and preview up to 10 rows of a table. Inspect foreign-key relationships and indexes with sizes. Execute a single modifying statement (INSERT, UPDATE, DELETE, CREATE, ALTER, DROP, TRUNCATE) that commits. Read passive resources for the table list and per-table schema details.
When to use it
Useful when an assistant needs to explore an unfamiliar PostgreSQL schema, answer questions from live data, or check query plans and indexes without leaving the chat. Suited to local development and analysis where a database connection is already available.
Requirements
Runs locally over stdio as a Python package (Python 3.11+) launched with uvx, and needs a reachable PostgreSQL database. Required environment variables: POSTGRES_HOST, POSTGRES_PORT, POSTGRES_USER, POSTGRES_DB; POSTGRES_PASSWORD is optional. POSTGRES_READ_QUERY_LIMIT caps rows returned by read queries. An MCP-compatible client is needed.
Before you install
The server includes a write tool that can modify data and schema and commits changes; the README calls it destructive and advises against auto-approving it and reviewing generated SQL first. Use a least-privilege, ideally read-only database user. POSTGRES_PASSWORD is a secret; do not commit .env files or client configs containing credentials.

Installation

In SourceWeft

  1. Open PostgreSQL MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

PostgreSQL MCP Server

A Python Model Context Protocol (MCP) server for inspecting and querying PostgreSQL databases from MCP-compatible clients. It provides schema discovery, safe read-only query execution, query explanation, table previews, index analysis, relationship inspection, and PostgreSQL resources for table metadata.

Features

  • List public tables and inspect table schemas
  • Execute read-only SQL in a PostgreSQL read-only transaction
  • Explain query plans without executing the target query directly
  • Preview table rows with a fixed limit
  • Inspect foreign-key relationships and indexes
  • Expose passive MCP resources for table lists and schema details

Safety Model

postgresql_execute_read_query runs with PostgreSQL read-only transaction mode, caps returned rows by POSTGRES_READ_QUERY_LIMIT, and rolls back after execution. The server also includes postgresql_execute_write_query, which only accepts a single INSERT, UPDATE, DELETE, CREATE, ALTER, DROP, or TRUNCATE statement and can modify data/schema if the connected database user has permission. Do not auto-approve write-capable tools in your MCP client. For public or shared use, run the server with a dedicated read-only PostgreSQL user.

Requirements

  • Python 3.11+
  • PostgreSQL database
  • MCP-compatible client such as Claude Desktop, Cursor, VS Code, or another MCP host

Installation

When published to PyPI, install or run the server like a standard Python MCP package:

bash
uvx mdev-postgresql-mcp-server

For local development from source:

bash
git clone https://github.com/musaddiq-dev/postgresql-mcp-server.gitcd postgresql-mcp-serverpython -m venv .venvsource .venv/bin/activatepip install -e .

Configuration

Copy the example environment file and update it with your database connection details.

bash
cp .env.example .env
VariableDescriptionRequiredDefault
POSTGRES_HOSTPostgreSQL hostYeslocalhost
POSTGRES_PORTPostgreSQL portYes5432
POSTGRES_USERPostgreSQL usernameYesNone
POSTGRES_PASSWORDPostgreSQL passwordNoNone
POSTGRES_DBPostgreSQL database nameYesNone
LOG_LEVELPython logging level written to stderrNoINFO
POSTGRES_READ_QUERY_LIMITMaximum rows returned by read queriesNo1000

Example read-only user:

sql
CREATE USER mcp_readonly WITH PASSWORD 'change-me';GRANT CONNECT ON DATABASE your_database TO mcp_readonly;GRANT USAGE ON SCHEMA public TO mcp_readonly;GRANT SELECT ON ALL TABLES IN SCHEMA public TO mcp_readonly;ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT SELECT ON TABLES TO mcp_readonly;

Running

bash
mdev-postgresql-mcp-server

From a local checkout before PyPI publication, run:

bash
python -m postgresql_mcp_server.server

MCP Client Configuration

For published installs, prefer uvx. MCP servers using stdio must write protocol messages only to stdout; this server writes logs to stderr through Python logging.

Claude Desktop / Cursor / Windsurf / Cline

Most MCP clients accept this mcpServers JSON shape:

json
{  "mcpServers": {    "postgresql": {      "command": "uvx",      "args": ["mdev-postgresql-mcp-server"],      "env": {        "POSTGRES_HOST": "localhost",        "POSTGRES_PORT": "5432",        "POSTGRES_USER": "mcp_readonly",        "POSTGRES_PASSWORD": "change-me",        "POSTGRES_DB": "your_database"      }    }  }}

For local development from this repository, use the installed console script path instead:

json
{  "mcpServers": {    "postgresql": {      "command": "/absolute/path/to/postgresql-mcp-server/.venv/bin/mdev-postgresql-mcp-server",      "args": [],      "env": {        "POSTGRES_HOST": "localhost",        "POSTGRES_PORT": "5432",        "POSTGRES_USER": "mcp_readonly",        "POSTGRES_PASSWORD": "change-me",        "POSTGRES_DB": "your_database"      }    }  }}

Claude Code CLI

bash
claude mcp add postgresql \  --env POSTGRES_HOST=localhost \  --env POSTGRES_PORT=5432 \  --env POSTGRES_USER=mcp_readonly \  --env POSTGRES_PASSWORD=change-me \  --env POSTGRES_DB=your_database \  -- uvx mdev-postgresql-mcp-server

VS Code MCP

VS Code uses the same command/args/env model in its MCP configuration:

json
{  "servers": {    "postgresql": {      "type": "stdio",      "command": "uvx",      "args": ["mdev-postgresql-mcp-server"],      "env": {        "POSTGRES_HOST": "localhost",        "POSTGRES_PORT": "5432",        "POSTGRES_USER": "mcp_readonly",        "POSTGRES_PASSWORD": "change-me",        "POSTGRES_DB": "your_database"      }    }  }}

Tools

ToolPurposeSafety
postgresql_list_tablesList public base tablesRead-only
postgresql_describe_tableShow columns and metadata for a tableRead-only
postgresql_execute_read_queryRun bounded SQL under read-only transaction modeRead-only
postgresql_execute_write_queryRun a single approved modifying SQL statement and commitDestructive
postgresql_explain_queryReturn PostgreSQL EXPLAIN output for a single queryRead-only
postgresql_get_database_summaryReturn database version and table countRead-only
postgresql_get_relationshipsInspect foreign-key relationshipsRead-only
postgresql_analyze_indexesInspect indexes and sizesRead-only
postgresql_preview_tableReturn up to 10 rows from a tableRead-only
postgresql_search_sql_definitionsSearch public SQL routines/functionsRead-only

Resources

  • postgres://list_tables returns public table names.
  • postgres://schema/{table_name} returns a generated schema statement for a table.

Smoke Check

Without a database, verify syntax with:

bash
python -m py_compile src/postgresql_mcp_server/server.py

With a configured database, start the server and use your MCP client to call list_tables.

Distribution

This server is published through the standard Python MCP distribution path:

  • PyPI package: mdev-postgresql-mcp-server
  • MCP Registry name: io.github.musaddiq-dev/postgresql-mcp-server
  • Runtime hint: uvx
  • Transport: stdio

The mcp-name marker at the top of this README is required for MCP Registry ownership verification. Users should prefer uvx mdev-postgresql-mcp-server in local MCP client configurations.

Security Notes

  • Do not commit .env or MCP client configs containing credentials.
  • Use least-privilege database users.
  • Treat execute_write_query as destructive and require explicit user approval in your MCP client.
  • Review generated SQL before running write-capable tools.

License

MIT

Source: README.md at commit 3e4ecf6

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts