@mhdd_24/dbeaver-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PG_QA_HOST | No | Alternative prefix for QA database host. | |
| PG_QA_PORT | No | Alternative prefix for QA database port. | |
| PG_QA_USER | No | Alternative prefix for QA database user. | |
| PG_DEV_HOST | No | Alternative prefix for development database host. | |
| PG_DEV_PORT | No | Alternative prefix for development database port. | |
| PG_DEV_USER | No | Alternative prefix for development database user. | |
| PG_ALLOW_WRITE | No | Alternative to DBEAVER_ALLOW_WRITE. Set to 'true' to allow write operations. Defaults to 'false' (read-only). | |
| PG_QA_DATABASE | No | Alternative prefix for QA database name. | |
| PG_QA_PASSWORD | No | Alternative prefix for QA database password. | |
| DBEAVER_PROFILE | No | Active profile to use (dev or qa). Optional. | |
| DBEAVER_QA_HOST | No | Hostname of the QA database. | |
| DBEAVER_QA_PORT | No | Port of the QA database. | |
| DBEAVER_QA_USER | No | Username for the QA database. | |
| PG_DEV_DATABASE | No | Alternative prefix for development database name. | |
| PG_DEV_PASSWORD | No | Alternative prefix for development database password. | |
| DBEAVER_DEV_HOST | No | Hostname of the development database. | |
| DBEAVER_DEV_PORT | No | Port of the development database. | |
| DBEAVER_DEV_USER | No | Username for the development database. | |
| PG_QUERY_MAX_ROWS | No | Alternative to DBEAVER_QUERY_MAX_ROWS. Maximum number of rows returned per query. | |
| DBEAVER_ALLOW_WRITE | No | Set to 'true' to allow write operations. Defaults to 'false' (read-only). | |
| DBEAVER_QA_DATABASE | No | Name of the QA database. | |
| DBEAVER_QA_PASSWORD | No | Password for the QA database. | |
| DBEAVER_DEV_DATABASE | No | Name of the development database. | |
| DBEAVER_DEV_PASSWORD | No | Password for the development database. | |
| DBEAVER_QUERY_MAX_ROWS | No | Maximum number of rows returned per query. Defaults to '500'. | |
| PG_STATEMENT_TIMEOUT_MS | No | Alternative to DBEAVER_STATEMENT_TIMEOUT_MS. Query timeout in milliseconds. | |
| DBEAVER_STATEMENT_TIMEOUT_MS | No | Query timeout in milliseconds. |
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 |
|---|---|
| db_set_profileA | Set the sticky session connection profile to "dev" or "qa" (or "default"). Call when the user says dbprofile=dev, dbprofile=qa, use Dev DB, switch to QA, etc. Later tools reuse this profile automatically — no host/password in chat. Credentials are loaded from DBEAVER_DEV_* / DBEAVER_QA_* (or PG_DEV_* / PG_QA_*) in mcp.json. |
| db_statusA | Show current sticky PostgreSQL profile, host, database, write mode, and a live SELECT 1 health check. Optional profile arg for a one-shot check without changing the sticky session. |
| db_list_databasesA | List databases on the active profile server (or optional one-shot profile=dev|qa). |
| db_list_schemasA | List non-system schemas. Optional database and/or profile (dev|qa) override. |
| db_list_tablesA | List tables/views for a schema (default public). Optional database and/or profile override. |
| db_describe_tableA | Describe columns for a table or view. Optional schema, database, and/or profile override. |
| db_queryA | Run SQL against the sticky session profile (or optional profile=dev|qa for one call). Read-only by default. Optional database name and maxRows. Do not ask the user for connection host/password — use profiles. |
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 7 tools
Each tool has a distinct purpose: profile management, status checking, listing databases/schemas/tables, describing tables, and running queries. No overlap or ambiguity between them.
All tools follow a consistent 'db_' prefix with clear verb_noun naming (set_profile, list_databases, describe_table, etc.). Even the single-word tools like db_status and db_query are clear and fit the pattern.
Seven tools is well within the ideal range for a database exploration server. Each tool provides a necessary function without redundancy, making the set feel intentionally scoped.
The toolset covers the core read-only workflow: setting profiles, checking status, exploring database structure, and querying. The only notable gap is the lack of write operations (insert/update/delete), but the read-only default suggests this is intentional, so it's a minor limitation.