dbeaver-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DBEAVER_MCP_STATE | No | Where the backup-banner marker lives | ~/.dbeaver-mcp |
| DBEAVER_WORKSPACE | No | Folder containing `General/.dbeaver/data-sources.json` | auto-detected |
| DBEAVER_MCP_MAX_BYTES | No | Total result payload cap per call | 262144 |
| DBEAVER_MCP_READ_ONLY | No | `true` unregisters every write tool | false |
| DBEAVER_MCP_KNOWN_HOSTS | No | Path list for host key lookup | ~/.ssh/known_hosts |
| DBEAVER_MCP_SSL_ROOT_CERT | No | CA bundle for `verify-ca` / `verify-full` | ~/.postgresql/root.crt |
| DBEAVER_MCP_DISABLED_TOOLS | No | Tool names to remove from the surface | none |
| DBEAVER_MCP_MAX_CELL_BYTES | No | Per-cell cap; `bytea` is summarised, never dumped | 2048 |
| DBEAVER_MCP_LOCK_TIMEOUT_MS | No | Server-side lock timeout | 10000 |
| DBEAVER_MCP_IDLE_TX_TIMEOUT_MS | No | Kills sessions left idle in a transaction | 30000 |
| DBEAVER_MCP_ALLOWED_CONNECTIONS | No | Comma-separated names/ids, `*`/`?` wildcards | all |
| DBEAVER_MCP_SSH_HOST_KEY_POLICY | No | `strict`, `tofu` (trust on first use), `insecure` (no verification) | strict |
| DBEAVER_MCP_STATEMENT_TIMEOUT_MS | No | Server-side statement timeout | 30000 |
| DBEAVER_MCP_WRITABLE_CONNECTIONS | No | Narrower list that may be written to | = allowed |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_connectionsA | List DBeaver Community connections (names, hosts, SSH hop). Passwords are never returned. |
| test_connectionA | Open the DBeaver connection (starts a verified SSH tunnel if needed) and run SELECT 1. |
| execute_queryA | Run read-only SQL inside a READ ONLY transaction. Multiple SELECTs return every result set (not only the last). SSH tunnels open automatically. |
| write_queryA | Run INSERT/UPDATE/DELETE/DDL. Requires an exact connection name or id. Several statements in one string run on one connection; more than one write is wrapped in a transaction. |
| run_scriptB | Run several SQL statements on one connection. Requires an exact connection name or id. Defaults to a transaction when any statement writes. |
| inspect_sequencesA | Compare serial/identity sequences to MAX(column). needs_reset is true when the table is ahead of the sequence (typical after a dump or manual INSERT). |
| explain_queryA | Show the Postgres query plan for one statement. analyze: true runs it for real timings and is refused on anything that writes. |
| fix_sequencesA | Reset serial/identity sequences that have fallen behind MAX(column) — the duplicate-key state a dump leaves behind. Defaults to a dry run; pass apply: true to write. |
| trust_ssh_hostA | Show the SSH host key fingerprint for a tunnelled connection, and record it in known_hosts only when the user confirms that exact fingerprint. Use this when a tunnel fails with "Unknown SSH host key". |
| list_schemasA | List non-system schemas on a DBeaver connection. |
| list_tablesA | List tables in a schema for a DBeaver connection. |
| describe_tableB | Describe columns of a table on a DBeaver connection. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools have distinct purposes, but execute_query and run_script both execute SQL, which could cause confusion. Descriptions clarify that execute_query is read-only while run_script handles mixed statements, so the overlap is manageable.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., test_connection, list_schemas, fix_sequences). No mixed conventions or vague verbs.
12 tools is well within the ideal 3-15 range and each tool addresses a specific database operation or connection concern. The count feels appropriately scoped for a DBeaver MCP server.
The surface covers connection testing, read/write queries, query planning, script execution, sequence management, SSH trust, and schema/table inspection. Minor gaps like view or procedure listing exist, but core workflows are well covered.