postgres-dba-mcp
Related Servers
Alternatives to postgres-dba-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to safely inspect and query PostgreSQL databases with read-only enforcement, row/timeout limits, and audit logging, providing tools for schema/table listing, read-only queries, query explanations, and table statistics.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to inspect PostgreSQL health, tune indexes, review and optimize EXPLAIN plans, understand schemas for context-aware SQL, and execute SQL safely with read-only/restricted or unrestricted access modes.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to safely interact with PostgreSQL databases, perform queries, inspect schemas, and analyze query performance.2ISC
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to inspect and monitor PostgreSQL databases with read-only DBA tools for performance analysis, bloat detection, locks/deadlocks, autovacuum, schema discovery, replication, and maintenance recommendations.-
- AlicenseNot gradedqualityBmaintenanceEnables AI tools to query a PostgreSQL database, read its schema, list and describe tables, and explain queries while enforcing read-only transactions, row and byte limits, and timeouts.1MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to inspect and monitor PostgreSQL 12-18 databases through natural language, covering performance analysis, slow-query identification, bloat and lock detection, autovacuum health, replication/WAL status, and schema exploration. All operations are read-only and work without requiring any extensions, though pg_stat_statements and pg_stat_monitor optionally enhance query analytics.-
TDQS
Scored across 10 tools
Each tool has a largely distinct purpose: locks vs. health vs. query plans vs. object listing. The main fuzzy pair is analyze_query_indexes (analyze a supplied query list) vs. analyze_workload_indexes (analyze pg_stat_statements workload), which an agent could confuse, but the descriptions make the input difference clear. get_object_details vs. list_objects/list_schemas are also adequately separated.
All ten tools follow a consistent snake_case verb_noun pattern (analyze_*, get_*, list_*, execute_sql, explain_query). No mixed casing or inconsistent verb styles. The convention makes the action+resource of each tool predictable.
Ten tools is well within the ideal 3-15 range for a DBA diagnostic server. Each tool covers a distinct diagnostic area (locks, health, indexes, execution, object introspection) with no apparent filler.
The surface covers the main read-only DBA workflows: health checks, lock analysis, slow-query inspection, plan explanation, index recommendations, and schema/object exploration. The deliberate read-only stance (no cancel/terminate, no config parameter inspection or pg_stat_activity detail dump) leaves some operational gaps, but they are minor and consistent with the server's stated scope.