MCP-PostgreSQL-Ops is a PostgreSQL database monitoring and operations tool that enables natural language diagnostics across PostgreSQL 12-17 databases. Key features of MCP-PostgreSQL-Ops: - Natural language queries for diagnosing slow queries, table bloat, replication lag, WAL health, and database locks. - Schema discovery with detailed relationship mapping and database structure exploration. - Intelligent maintenance monitoring including VACUUM effectiveness and autovacuum analysis. - Multi-database operations for seamless cross-database monitoring and analysis. - Production-safe read-only operations compatible with AWS RDS/Aurora using standard user permissions. - Enhanced query analytics when pg_stat_statements and pg_stat_monitor extensions are installed. - Real-time monitoring for connections, locks, background processes, and checkpoint statistics.

MCP Server for PostgreSQL Operations and Monitoring

[](https://opensource.org/licenses/MIT)

[](https://smithery.ai/server/@call518/mcp-postgresql-ops) [](https://www.buymeacoffee.com/call518)

[](https://github.com/call518/MCP-PostgreSQL-Ops/actions/workflows/pypi-publish.yml)

---

Architecture & Internal (DeepWiki)

[](https://deepwiki.com/call518/MCP-PostgreSQL-Ops)

---

Overview

MCP-PostgreSQL-Ops is a professional MCP server for PostgreSQL database operations, monitoring, and management. Supports PostgreSQL 12-17 with comprehensive database analysis, performance monitoring, and intelligent maintenance recommendations through natural language queries. Most features work independently, but advanced query analysis capabilities are enhanced when pg_stat_statements and (optionally) pg_stat_monitor extensions are installed.

---

Features

🔧 Advanced Capabilities

Tool Usage Examples

📸 More Examples with Screenshots →

---

---

---

⭐ Quickstart (5 minutes)

> Note: The postgresql container included in docker-compose.yml is intended for quickstart testing purposes only. You can connect to your own PostgreSQL instance by adjusting the environment variables as needed.

> If you want to use your own PostgreSQL instance instead of the built-in test container: > - Update the target PostgreSQL connection information in your .env file (see POSTGRES_HOST, POSTGRES_PORT, POSTGRES_USER, POSTGRES_PASSWORD, POSTGRES_DB). > - In docker-compose.yml, comment out (disable) the postgres and postgres-init-extensions containers to avoid starting the built-in test database.

Flow Diagram of Quickstart/Tutorial

1. Environment Setup

> Note: While superuser privileges provide access to all databases and system information, the MCP server also works with regular user permissions for basic monitoring tasks.

git clone https://github.com/call518/MCP-PostgreSQL-Ops.git
cd MCP-PostgreSQL-Ops
Check and modify .env file
cp .env.example .env
vim .env

### No need to modify defaults, but if using your own PostgreSQL server, edit below:
POSTGRES_HOST=host.docker.internal
POSTGRES_PORT=15432  # External port for host access (mapped to internal 5432)
POSTGRES_USER=postgres
POSTGRES_PASSWORD=changeme!@34
POSTGRES_DB=ecommerce # Default connection DB. Superusers can access all DBs.

> Note: PGDATA=/data/db is preconfigured for the Percona PostgreSQL Docker image, which requires this specific path for proper w