dbeaver-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DBEAVER_ENCRYPTION_KEY | No | Override credential encryption key (hex) (default key used otherwise) | Default |
| DBEAVER_WORKSPACE_PATH | No | Override workspace path (auto-discovered by default) | Auto-discovered |
| DBEAVER_DRIVERS_XML_PATH | No | Override drivers.xml path (auto-discovered by default) | Auto-discovered |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workspacesA | List all discovered DBeaver workspaces with their projects and data source locations. |
| list_connectionsA | List all configured database connections from DBeaver. Optionally filter by workspace_path from list_workspaces. Args: workspace_path: Optional workspace path to filter connections. If empty, returns all. |
| execute_sqlA | Execute a read-only SQL query on a specified DBeaver database connection. Only SELECT, SHOW, DESCRIBE, EXPLAIN, WITH statements are allowed. Write operations are strictly prohibited. Args: connection_name: The name of the database connection (as shown in list_connections). sql: The read-only SQL query to execute. |
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 3 tools
Each tool has a distinct purpose: listing workspaces, listing connections, and executing SQL queries. No overlap in functionality.
All tools follow a consistent verb_noun pattern using snake_case (list_workspaces, list_connections, execute_sql).
Three tools are appropriate for the server's focused purpose of managing database connections and executing read-only SQL queries. Each tool serves a clear role.
The tool set covers workspace discovery, connection listing, and SQL execution, but lacks schema exploration (e.g., listing tables or describing schemas), which is a notable gap for a database tool.