MCP PostgreSQL Ops
Verified🐘 Give AI assistants full PostgreSQL DBA superpowers — 30+ tools for performance analysis, bloat detection, lock/deadlock monitoring, autovacuum & schema inspection. No extensions required. PG 12-18.
Set up this server
01 / Choose your client
02 / Before you connect
Authentication is not specified. Check the project instructions before connecting.
Project instructions03 / Add the configuration
claude mcp add --transport stdio 'mcp-postgresql-ops' -- 'uvx' '--python' '3.12' 'mcp-postgresql-ops'04 / Check it in your client
Open your client’s MCP settings and confirm the server connects and lists its tools. A copied configuration does not confirm a working connection.
More in Databases
Browse the full directoryBadge
Show this listing on your README and website
Your listing links back to your site with a do-follow link. Keep the badge on your README or site to stay verified (Pro removes this requirement).
Security profile
Exposure: Limited
Runs commands or loads code on your machine, but does not reach secrets or other agents.
What this server can reach, from a static read of the shipped code. Nothing was executed and nothing here is a verdict: a browser tool has to run commands and an API wrapper has to call its API. Decide what fits your setup.
Detected
- Runs shell commands
Spawns processes on your machine. Expected for command, browser and build tools.
- Reads local configuration files
Loads a .env, .npmrc or config file. Normal for a server that needs an API key.
- Runs unpinned packages at runtime
Executes npx or uvx without a version, so a compromised upstream release would run.
Dependencies with known advisories
None found in the lockfiles and manifests checked against OSV.dev.
Left out of the profile
17 pattern matches in documentation, configuration or CI files were recorded but are not part of the profile, because they do not run when the server does. The owner dashboard lists them.
37 of 37 tools · Observed tool names: 38/38
Observed tool names (38)
Reported by a complete handshake for the current saved configuration. Tools were listed, not invoked.
· 1.3.0
get_active_connectionsget_all_tables_statsget_async_io_statusget_autovacuum_activityget_autovacuum_statusget_bgwriter_statsget_current_database_infoget_database_bloat_overviewget_database_conflicts_statsget_database_listget_database_schema_infoget_database_size_infoget_database_statsget_index_io_statsget_index_usage_statsget_io_statsget_lock_monitoringget_per_backend_io_statsget_pg_stat_monitor_recent_queriesget_pg_stat_statements_top_queriesget_postgresql_configget_prompt_templateget_replication_statusget_running_vacuum_operationsget_server_infoget_table_bloat_analysisget_table_io_statsget_table_listget_table_relationshipsget_table_schema_infoget_table_size_infoget_user_functions_statsget_user_listget_vacuum_analyze_statsget_vacuum_effectiveness_analysisget_wait_eventsget_wal_statusget_wal_summarizer_statusDocumented tools (37)
From project documentation. A server handshake does not verify each tool’s description or behavior.
get_active_connections
❌ None
get_all_tables_stats
❌ None
get_async_io_status
❌ None
get_autovacuum_activity
❌ None
get_autovacuum_status
❌ None
get_bgwriter_stats
❌ None
get_current_database_info
❌ None
get_database_bloat_overview
❌ None
get_database_conflicts_stats
❌ None
get_database_list
❌ None
get_database_schema_info
❌ None
get_database_size_info
❌ None
get_database_stats
❌ None
get_index_io_stats
❌ None
get_index_usage_stats
❌ None
get_io_stats
❌ None
get_lock_monitoring
❌ None
get_per_backend_io_stats
❌ None
get_pg_stat_monitor_recent_queries
pgstatmonitor
get_pg_stat_statements_top_queries
pgstatstatements
get_postgresql_config
❌ None
get_replication_status
❌ None
get_running_vacuum_operations
❌ None
get_server_info
❌ None
get_table_bloat_analysis
❌ None
get_table_io_stats
❌ None
get_table_list
❌ None
get_table_relationships
❌ None
get_table_schema_info
❌ None
get_table_size_info
❌ None
get_user_functions_stats
⚙️ Config Required
get_user_list
❌ None
get_vacuum_analyze_stats
❌ None
get_vacuum_effectiveness_analysis
❌ None
get_wait_events
❌ None
get_wal_status
❌ None
get_wal_summarizer_status
❌ None
Tool change history
Nov 8, 2026, 03:24 AM UTC
Nov 1, 2026, 03:21 AM UTC
FAQ
Questions about MCP PostgreSQL Ops MCP Server
- How do I connect MCP PostgreSQL Ops MCP Server to Claude?
- Run `claude mcp add mcp-postgresql-ops -- uvx --python 3.12 mcp-postgresql-ops` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.
- Is MCP PostgreSQL Ops MCP Server free?
- The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
- What can MCP PostgreSQL Ops MCP Server do?
- MCP PostgreSQL Ops MCP Server documents 37 tools to the agent, including get_active_connections, get_all_tables_stats, get_async_io_status. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.