postgresql-mcp
Related Servers
Alternatives to postgresql-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server that connects AI assistants to any PostgreSQL database with 25 tools and role-based access control.25 npmMIT
- AlicenseBqualityNot gradedmaintenanceA universal MCP server that enables AI agents to securely manage PostgreSQL databases, make API requests, and execute SSH commands with features for database analysis, schema editing, and data operations.31-
- AlicenseAqualityDmaintenanceA production-grade MCP server that gives AI agents safe, authenticated access to a PostgreSQL database.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to securely interact with PostgreSQL databases through a standardized MCP interface, supporting SQL queries, schema inspection, and database management.MIT
- AlicenseNot gradedqualityDmaintenanceA PostgreSQL MCP server with AST-based security for safe database operations. Enables AI assistants to query and manage PostgreSQL databases securely.MIT
- AlicenseBqualityDmaintenanceA blazing fast MCP server that enables AI agents to interact with multiple PostgreSQL databases, providing functionality to list tables, inspect schemas, execute queries, and run transactions.4152 npmMIT
TDQS
Scored across 4 tools
The structured tools (create_table, list_tables, describe_table) have clear, distinct purposes, and execute_sql is explicitly a general SQL escape hatch. However, execute_sql overlaps with all of them, especially create_table, since table creation can be done through either tool.
All tool names follow the same verb_noun snake_case pattern: create_table, list_tables, describe_table, execute_sql. There are no mixed conventions or inconsistent verb styles.
Four tools is a reasonable, well-scoped set for a PostgreSQL server: three schema-oriented helpers plus one arbitrary SQL tool. Each tool has a clear role and none feel redundant or missing.
The set covers schema creation, listing, and inspection, and execute_sql provides full database access as a fallback. Row-level CRUD and operations like ALTER/DROP are not exposed as first-class tools, but they can be handled through execute_sql, leaving only minor gaps.