@mhdd_24/dbeaver-mcp
Provides tools for PostgreSQL database exploration and SQL querying, including listing databases, schemas, tables, describing table columns, running read-only queries, and switching between dev/QA profiles.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@mhdd_24/dbeaver-mcp list tables in schema public for database postgres"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@mhdd_24/dbeaver-mcp
MCP server for PostgreSQL / DBeaver-style exploration and SQL from Cursor (or any MCP client). Same architecture as @mhdd_24/pgadmin-mcp.
Say "db status", "list databases", or "run this SQL on Dev" in chat — the assistant calls the matching tools.
Full documentation: docs/WIKI.md
Tools
Tool | Role |
| Sticky session switch: |
| Sticky + active profile, host, |
| List databases on active (or one-shot) profile server |
| List user schemas |
| List tables/views in a schema |
| Column metadata |
| Run SQL (read-only by default) |
Profiles (no connection details in chat)
Put both Dev and QA credentials in
mcp.json(DBEAVER_DEV_*,DBEAVER_QA_*— or reusePG_DEV_*/PG_QA_*).Say
dbprofile=qaordbprofile=dev— the assistant callsdb_set_profile.Later tools reuse that sticky profile until you switch or the MCP process restarts.
Optional one-shot: pass
profile: "qa"on a single tool without changing sticky.databasestill means the logical DB name on that server (e.g.transboard), not the env profile.
Related MCP server: pgEdge Postgres MCP Server
Safety
Read-only by default — only
SELECT/WITH…SELECT/EXPLAIN/SHOW/VALUESSet
DBEAVER_ALLOW_WRITE=true(orPG_ALLOW_WRITE=true) to allow writesDBEAVER_QUERY_MAX_ROWS/PG_MAX_ROWScaps returned rows; timeout viaDBEAVER_STATEMENT_TIMEOUT_MS/PG_QUERY_TIMEOUT_MS
Install / run
npm i -g @mhdd_24/dbeaver-mcp
# or from source:
git clone https://github.com/Mhdd-24/DBeaver-MCP.git
cd DBeaver-MCP
npm install
npm run build
node dist/index.jsCursor mcp.json
"dbeaver": {
"command": "npx",
"args": ["-y", "@mhdd_24/dbeaver-mcp"],
"env": {
"DBEAVER_PROFILE": "dev",
"DBEAVER_DEV_HOST": "192.168.1.141",
"DBEAVER_DEV_PORT": "5432",
"DBEAVER_DEV_USER": "postgres",
"DBEAVER_DEV_PASSWORD": "YOUR_PASSWORD",
"DBEAVER_DEV_DATABASE": "postgres",
"DBEAVER_QA_HOST": "192.168.1.131",
"DBEAVER_QA_PORT": "5432",
"DBEAVER_QA_USER": "postgres",
"DBEAVER_QA_PASSWORD": "YOUR_PASSWORD",
"DBEAVER_QA_DATABASE": "postgres",
"DBEAVER_ALLOW_WRITE": "false",
"DBEAVER_QUERY_MAX_ROWS": "500"
}
}Restart Cursor after saving.
Example prompts
dbprofile=qa
dbprofile=dev
db status
list databases
list tables in schema transc for database transboard
describe table translations schema transc database transboard
run: SELECT version();
Available Tools
7 toolsdb_describe_tableA
Describe columns for a table or view. Optional schema, database, and/or profile override.
Inputs: table (required), schema, profile, database.
db_list_databasesA
List databases on the active profile server (or optional one-shot profile=dev|qa).
Inputs: profile.
db_list_schemasA
List non-system schemas. Optional database and/or profile (dev|qa) override.
Inputs: profile, database.
db_list_tablesA
List tables/views for a schema (default public). Optional database and/or profile override.
Inputs: schema, profile, database.
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.
Inputs: sql (required), maxRows, profile, database.
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.
Inputs: profile (required), verify.
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.
Inputs: profile, database.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Analytical memory for AI agents: a real Postgres queried in plain English over MCP. One command.
Hosted PostgreSQL MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Text-to-SQL MCP server: read-only queries on PostgreSQL, MySQL and SQL Server with your real schema
Query PostgreSQL databases in plain English — LLM-generated, safety-validated SQL.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables interaction with PostgreSQL databases through MCP, allowing users to explore database structures, inspect table schemas, and execute read-only SQL queries.-

pgEdge Postgres MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceEnables SQL queries against PostgreSQL databases through MCP-compatible clients and includes a natural language agent for forming SQL queries from natural language.247PostgreSQL- AlicenseNot gradedqualityDmaintenanceEnables interaction with PostgreSQL databases through MCP, supporting queries, DDL, DML, and schema inspection.35 PyPI6MIT
- AlicenseAqualityDmaintenanceSupports CRUD and DDL operations on PostgreSQL databases via MCP, enabling query, insert, update, delete, and schema changes through natural language.69 npmMIT