"DBeaver" matching MCP servers:

Enables AI agents to query local Postgres databases through saved DBeaver Community connections, including SSH-tunnelled ones, without exposing credentials.

Enables AI assistants to explore and query PostgreSQL, MySQL, MariaDB, SQLite, SQL Server and Oracle databases by reusing connections already configured in DBeaver, with no separate credentials to manage. Queries run read-only and rolled back by default, so schema exploration, data reads and query plans are safe on existing dev, test and production connections.

MCP server that reads DBeaver database configurations and provides SQL execution via existing JDBC drivers — no extra driver downloads needed.

Enables Codex to safely discover and query PostgreSQL connections saved in DBeaver through structured, parameterized read-only SELECTs, including catalog inspection, query analysis/execution, settings retrieval, and sanitized log summaries. It enforces read-only transactions, server-side validation, and bounded access without accepting free-form SQL or exposing credentials.

Gives MCP clients query access to the PostgreSQL databases already configured in DBeaver, reusing the saved connection credentials so nothing has to be copied elsewhere and limiting exposure to an explicit allowlist. Every statement runs inside a read-only transaction with a timeout and row cap, with tools for listing connections and tables, describing a table, and running single ad-hoc queries.

Enables 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.

Lets Claude Code, Codex, and OpenCode query and inspect databases using reused DBeaver connections and native drivers, with configurable read-only access and tool restrictions.