M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionPostgres MCP ProConfigurable read/write access and performance analysis for PostgreSQL MCPDBHubBytebase's official, minimalist two-tool database MCP server
FMRS48 / 100 · D74 / 100 · B
Reliability9 / 2013 / 20
Security and permissions7 / 2013 / 20
Maintenance10 / 2016 / 20
Documentation11 / 2015 / 20
Setup experience11 / 2017 / 20
Best for
  • PostgreSQL developers needing deep performance analysis and index tuning
  • DBAs who need read-only access and health checks in production
  • Teams that want AI assistants to help with database optimization and monitoring
  • Scenarios wanting the smallest possible tool count and lowest context-window overhead for database access
  • Cases needing to grant non-technical teammates safe, read-only database access
Not for
  • Users needing full write access but wanting safety controls (restricted mode is read-only)
  • Users of non-PostgreSQL databases
  • Users needing real-time monitoring or alerting (this tool is analytical)
  • Scenarios needing database administration operations (creating indexes, altering schema) rather than just querying (DBHub is positioned as a query tool, not a DBA management tool)
Required permissions
  • Database connection credentials (connection URI)
  • Read-write or read-only database access (depending on access mode)
  • Optional: permission to load extensions (pg_stat_statements, hypopg)
  • Optional: OpenAI API key for experimental LLM index tuning
  • Requires a database connection string (DSN), which may contain sensitive credentials
  • execute_sql can run arbitrary SQL (including writes) by default — must be constrained via read-only mode or the underlying database account's own permissions
Risks and side effects
  • Unrestricted mode can allow SQL that might damage or delete data
  • SQL parsing may not prevent all bypasses of read-only restrictions if unsafe procedural languages are enabled
  • Connection credentials may be stored in plaintext in MCP client configuration
  • Index tuning search may consume significant database resources
  • Under default settings, if the connected database account has write access, execute_sql could let the assistant perform an unintended write or delete — pair with a read-only database account in production
  • The DSN contains a plaintext password — pay attention to the access permissions on wherever the config is stored
Supported clientsClaude Desktop, Cursor, Windsurf, Goose, Qodo GenClaude Desktop, Claude Code, VS Code, Cursor, Zed
Tools92