multigres-mcp
Related Servers
Alternatives to multigres-mcp
- AlicenseAqualityDmaintenancePostgres Pro is an open source Model Context Protocol (MCP) server built to support you and your AI agents throughout the entire development process—from initial coding, through testing and deployment, and to production tuning and maintenance.93,445MIT
Related Servers
- AlicenseAqualityCmaintenanceProvides PostgreSQL database management and analysis via MCP, enabling schema exploration, query execution, performance monitoring, and database health checks.3633 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides tools for managing PostgreSQL databases through the Managed DB API, including project creation, table management, migrations, backups, and more.-
- AlicenseAqualityAmaintenanceRead-only PostgreSQL performance auditing via MCP. Collects metrics from PostgreSQL system views, applies deterministic checks for index, query, vacuum, configuration, and connection issues, and returns structured findings for MCP clients.6MIT
- AlicenseAqualityAmaintenanceGoverned PostgreSQL DBA operations — slow-query, bloat, and blocking-lock RCA, index management, vacuum/analyze, and replication lag, with unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.35MIT
- FlicenseNot gradedqualityAmaintenanceEnables natural-language PostgreSQL operations and monitoring across PG 12-18 without requiring extensions, covering performance analysis, slow-query identification, bloat detection, lock and connection monitoring, autovacuum inspection, replication/WAL status, and schema relationship discovery. All operations are read-only and production-safe, working with regular user permissions on RDS/Aurora as well as self-hosted instances.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to monitor and administer PostgreSQL 12-18 databases through natural language, covering performance and slow-query analysis, table bloat detection, connection and lock monitoring, autovacuum and maintenance recommendations, and schema discovery. All operations are read-only and work with regular user permissions, requiring no extensions unless optional query-analytics features are desired.-
TDQS
Scored across 9 tools
The two index advisors are cleanly separated by input source (user-supplied SELECTs vs. pg_stat_statements workload), and read paths (list_schemas, list_objects, get_object_details) are distinct. Minor overlap exists between explain_query and execute_sql's EXPLAIN mode, and between get_top_queries and diagnose's slow-query/log checks, but descriptions make the intended split clear.
Nearly all tools follow a predictable snake_case verb_noun pattern (list_schemas, list_objects, get_top_queries, analyze_workload_indexes). The lone bare verb 'diagnose' is the only deviation, though it is still readable and distinct.
Nine tools is well-scoped for a read-only Postgres diagnostics/monitoring server, with no redundant entries and each tool earning its place. Nothing feels padded or missing at the count level.
The surface covers discovery, inspection, ad-hoc querying, plan explanation, index advising, and health checks — a solid lifecycle for a diagnostic (non-mutating) server. Gaps are minor: no direct access to server settings/pg_settings or explicit index list, though get_object_details and diagnose cover much of that indirectly.