PostgreSQL MCP Server
Related Servers
Alternatives to PostgreSQL MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables comprehensive PostgreSQL database monitoring, analysis, and management through natural language queries. Provides performance insights, bloat analysis, vacuum monitoring, and intelligent maintenance recommendations across PostgreSQL versions 12-17.34161MIT
- AlicenseBqualityDmaintenanceEnables comprehensive PostgreSQL database management including index tuning, query plan analysis, health monitoring, schema-aware SQL generation, and safe SQL execution with configurable access control for both development and production environments.9MIT
- AlicenseAqualityCmaintenanceProvides PostgreSQL database management and analysis via MCP, enabling schema exploration, query execution, performance monitoring, and database health checks.3635 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to interact deeply with PostgreSQL databases—query data, manage schema, analyze performance, and administer the database.67 npm4MIT
- AlicenseNot gradedqualityDmaintenanceEnables safe interaction with PostgreSQL databases through read-only queries, schema exploration, and performance analysis.67 npmMIT
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to manage, monitor, and optimize PostgreSQL databases with over 200 specialized tools for operations, security, performance tuning, and diagnostics.47 npm9MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: analyze_database focuses on configuration and performance analysis, debug_database targets issue troubleshooting, and get_setup_instructions provides installation guidance. There is no overlap in functionality, making it easy for an agent to select the appropriate tool without confusion.
All tool names follow a consistent verb_noun pattern (analyze_database, debug_database, get_setup_instructions), using snake_case throughout. The naming is predictable and readable, with no deviations or mixed conventions.
With only 3 tools, the server feels thin for a PostgreSQL domain, which typically involves operations like querying, inserting, updating, or managing tables. While the tools cover analysis, debugging, and setup, the lack of core database interaction tools suggests an incomplete surface for typical agent workflows.
The tool set is severely incomplete for a PostgreSQL server, as it lacks basic CRUD operations (e.g., execute_query, create_table, insert_data) and management functions (e.g., list_tables, backup_database). This will cause significant agent failures when attempting to interact with the database beyond setup and diagnostics.