dbhub and MCP-PostgreSQL-Ops
The bytebase/dbhub tool is a multi-database generalist solution, while call518/MCP-PostgreSQL-Ops is a PostgreSQL specialist offering deeper monitoring and maintenance capabilities—making them complements for users who need both broad database access and advanced PostgreSQL-specific diagnostics.
About dbhub
bytebase/dbhub
Zero-dependency, token-efficient database MCP server for Postgres, MySQL, SQL Server, MariaDB, SQLite.
Implements just two core MCP tools—`execute_sql` and `search_objects`—with optional custom parameterized operations defined in TOML config, minimizing token overhead for AI context windows. Supports stdio, HTTP, and SSE transports for integration with Claude Desktop, VS Code, Cursor, and other MCP clients, plus includes a built-in web workbench for direct database interaction. Enforces safety guardrails including read-only mode, row limits, and query timeouts while enabling secure multi-database connections through SSH tunneling and SSL/TLS.
About MCP-PostgreSQL-Ops
call518/MCP-PostgreSQL-Ops
🔍Professional MCP server for PostgreSQL operations & monitoring: 30+ extension-independent tools for performance analysis, table bloat detection, autovacuum monitoring, schema introspection, and database management. Supports PostgreSQL 12-17.
Implements the Model Context Protocol (MCP) standard to integrate with AI assistants and language models, exposing PostgreSQL operations as callable tools through stdio transport. Leverages optional `pg_stat_statements` and `pg_stat_monitor` extensions for enhanced query analytics while maintaining core functionality on base PostgreSQL installations. Built with Python and containerized for Docker deployment, supporting RDS/Aurora environments with read-only permissions suitable for production use.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work