dbeaver-mcp
Related Servers
Alternatives to dbeaver-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with multiple SQL databases (PostgreSQL, MySQL, SQL Server, SQLite, Trino) through MCP, reusing existing DBeaver connections for queries, schema management, and transactions, with SSH tunneling and read-only mode support.22258 npmMIT
- AlicenseAqualityBmaintenanceEnables an AI assistant to query and browse multiple database engines read-only, with the ability to switch connections and engines dynamically during a session.1860 npmMIT
- AlicenseNot gradedqualityBmaintenanceLets Claude Code, Codex, and OpenCode query and inspect databases using reused DBeaver connections and native drivers, with configurable read-only access and tool restrictions.258 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to safely query and explore SQL Server and PostgreSQL databases with read-only access, supporting schema discovery, relationship exploration, and query execution.26 npm3MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with read-only access to inspect database schemas, preview data, and run safe queries across PostgreSQL, MySQL, MongoDB, and SQL Server. It enables AI tools to understand database structures and relationships automatically to generate more accurate code.9 npm7MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query and interact with MySQL, PostgreSQL, and SQLite databases through saved connections, supporting read-only exploration and optional write operations with safety controls.MIT
TDQS
Scored across 7 tools
Each tool targets a distinct discovery step: connections → schemas → tables → single-table structure → column search → query execution → execution plan. The only pair that could be confused, run_query and explain_query, is clearly separated by the 'shows the plan' description. No two tools appear to do the same thing.
All seven tools follow a strict snake_case verb_noun convention (list_*, describe_table, find_columns, run_query, explain_query). The verbs also reflect real semantic differences (list vs describe vs find), so the pattern is both consistent and informative.
Seven tools is well-scoped for a read-only database inspection server; each covers a distinct layer of the exploration workflow. Nothing feels padded, and no obvious step of the workflow is forced into an overloaded mega-tool.
The read-only exploration lifecycle (connect → schema → table → column → query → plan) is fully covered, with a sensible rollback-only write policy. Minor gaps remain: no way to list routines/sequences/triggers, no cross-connection or cross-schema text search for DDL/object names, and no connection health check beyond the 'can be used' flag in list_connections.