SERVER

MCP-PostgreSQL-Ops

Rank #2,244

smithery/call518/mcp-postgresql-ops

Monitor and analyze PostgreSQL databases with natural-language queries. Diagnose slow queries, locks, bloat, replication lag, and WAL health across single or multiple databases. Get safe, read-only insights with schema discovery and clear maintenance recommendations.

4 release tags
160 GitHub stars
by call518 (4 servers)View repository ↗
First listed
Aug 20, 2025
Last publish date
Oct 9, 2026
PURPOSE

What you can do with MCP-PostgreSQL-Ops

MCP-PostgreSQL-Ops exposes 37 predefined, read-only diagnostic tools for PostgreSQL operations and monitoring: connections, configuration, sizes, bloat, vacuum, locks, WAL, replication, I/O and (with extensions) top queries.

Suitable tasks
  • List databases, tables, schemas and relationships
  • Check active connections, locks and wait events
  • Analyze table bloat, autovacuum and vacuum effectiveness
  • Review index usage and table/index I/O stats
  • Monitor WAL, replication and background writer status
  • Find top queries via pg_stat_statements or pg_stat_monitor
CAPABILITIES AND LIMITATIONS

What MCP-PostgreSQL-Ops can and cannot do

Capabilities

37 tools: 26 extension-independent (server info, connections, config, schema, sizes, bloat, vacuum, locks, WAL, stats), 9 version-aware (I/O, bgwriter, replication, wait events, PG17/18-only summarizer and async I/O stats) and 2 that need pg_stat_statements or pg_stat_monitor. A database_name parameter lets one server cover several databases.

Documented tools (23 of 37)
  • get_server_info
  • get_active_connections
  • get_postgresql_config
  • get_database_list
  • get_table_list
  • get_table_schema_info
  • get_database_schema_info
  • get_table_relationships
  • get_user_list
  • get_index_usage_stats
  • get_database_size_info
  • get_table_size_info
  • get_vacuum_analyze_stats
  • get_table_bloat_analysis
  • get_database_bloat_overview
  • get_autovacuum_status
  • get_lock_monitoring
  • get_wal_status
  • get_database_stats
  • get_replication_status
  • get_wait_events
  • get_pg_stat_statements_top_queries
  • get_pg_stat_monitor_recent_queries
Limitations
  • No SQL execution at all: only predefined read-only queries
  • pg_stat_monitor is not available on managed engines such as RDS/Aurora
  • Some tools need track_functions or track_io_timing settings, or the pg_stat_statements/pg_stat_monitor extensions
  • Version-specific tools return "not available" on older PostgreSQL versions
  • No global row cap or statement timeout is documented; tools take a limit parameter
REQUIREMENTS

What you need before using MCP-PostgreSQL-Ops

DeclaredAPI keyCredentials declared

The registry listing declares required configuration before first use — typically an API key, token or connection string set via environment variables.

Declared by Glama, last synced Oct 16, 2026. Not independently verified by MCP Toplist.

Runtime
Python 3.12 via uvx/pip (mcp-postgresql-ops) or the docker-compose stack
Credentials
POSTGRES_HOST, POSTGRES_PORT, POSTGRES_USER, POSTGRES_PASSWORD, POSTGRES_DB env vars
Permissions
Read access to system catalogs; superuser not required (GRANT pg_read_all_stats recommended on RDS/Aurora)
Also needed
PostgreSQL 12–18; optional Bearer token auth (REMOTE_AUTH_ENABLE, REMOTE_SECRET_KEY) for streamable-http
INSTALLATION AND FIRST TASK

Connect MCP-PostgreSQL-Ops and confirm it works

  1. Install with pip install mcp-postgresql-ops, or run directly via uvx --python 3.12 mcp-postgresql-ops --type stdio
  2. Set the POSTGRES_* environment variables for a user with catalog read access
  3. Optionally enable pg_stat_statements/pg_stat_monitor and track_functions=pl, track_io_timing=on
  4. Register the uvx command in your MCP client, or run --type streamable-http on 127.0.0.1:8000

Install configuration unavailable. No registry publishes a machine-readable install config for this server — follow the repository README.

First successful task

Ask the agent "what version and settings is this Postgres server running?" so it calls get_server_info.

Expected: Server version and key configuration values returned without any SQL being executed by the agent.

ALTERNATIVES

When to choose another server

  • Postgres MCP#724

    You also want to run SQL and get index recommendations, not just statistics.

  • DBHub#63

    You need a query gateway with a health_check tool across several database engines.

  • PostgreSQL Database Management Server#10,284

    You need monitoring plus gated write and administration tools.

Compared side by side in PostgreSQL MCP servers.

Other servers by call518
View all call518 servers →
MAINTENANCE AND EVIDENCE

What changed, and when this was checked

First listed
Aug 20, 2025
Latest release tag
Oct 9, 2026
Version history
4 release tags tracked (below)
Requirements evidence
Declared by Glama, last synced Oct 16, 2026. Not independently verified by MCP Toplist.
Profile checked
Oct 9, 2026 against README
Ranking data as of
Oct 16, 2026
Registry sightings
  • Smithery ↗listed since Apr 26, 2026 · delisted, last seen Apr 30, 2026
  • PulseMCP ↗listed since Jun 4, 2026 · still listed
  • Glama ↗listed since Jun 4, 2026 · still listed

Do you maintain MCP-PostgreSQL-Ops? to correct or enrich this profile.

VERSIONS

GitHub releases (4)

No registry surfaces explicit version metadata for this server. The list below shows release tags from the linked GitHub repository.

3.3.5 · Apr 27, 20263.3.6 · Apr 28, 20263.3.7 · Apr 30, 20263.4.0 · Oct 9, 2026Apr 27, 2026Oct 9, 2026
VersionPublished
3.4.0Oct 9, 2026
3.3.7Apr 30, 2026
3.3.6Apr 28, 2026
3.3.5Apr 27, 2026
STANDING
#2,244of 144,396 active serversTop 5%

Ranks ahead of 142,152 of 144,396 servers on MCP Toplist.

Recent momentum
+12GitHub stars since Apr 27 (+8%)
BADGE

Show your rank

Maintain this server? Add the live rank badge to your README — it updates automatically as the leaderboard changes.

MCP Toplist: Top 5% of 144,396
Markdown
[![MCP Toplist](https://mcptoplist.com/badge/smithery%2Fcall518%2Fmcp-postgresql-ops.svg)](https://mcptoplist.com/server/smithery%2Fcall518%2Fmcp-postgresql-ops)
HTML
<a href="https://mcptoplist.com/server/smithery%2Fcall518%2Fmcp-postgresql-ops"><img src="https://mcptoplist.com/badge/smithery%2Fcall518%2Fmcp-postgresql-ops.svg" alt="MCP Toplist: Top 5% of 144,396" /></a>

Variants: append ?metric=score or ?metric=stars to the image URL.

FAQ

Frequently asked questions

Who maintains MCP-PostgreSQL-Ops?
MCP-PostgreSQL-Ops is maintained by call518, which publishes 4 MCP servers (11 total versions) tracked on MCP Toplist.
Is MCP-PostgreSQL-Ops listed on the Official MCP Registry?
MCP-PostgreSQL-Ops is not on the Official MCP Registry. It is listed on Smithery, PulseMCP and Glama.
How many versions does MCP-PostgreSQL-Ops have?
No registry surfaces explicit version metadata for MCP-PostgreSQL-Ops; MCP Toplist tracks 4 release tags from its GitHub repository, most recently published on Oct 9, 2026.
Where can I find the source code for MCP-PostgreSQL-Ops?
The source code for MCP-PostgreSQL-Ops is hosted at github.com/call518/mcp-postgresql-ops.
Used in projects

Do you run this server?

Community projects list the MCP servers behind real agents and apps. Publish yours and this page will link to it.

EXPLORE