Skip to main content
Glama
@mhdd_24/dbeaver-mcp

@mhdd_24/dbeaver-mcp

by Mhdd-24

@mhdd_24/dbeaver-mcp

npm version GitHub

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

db_set_profile

Sticky session switch: dev | qa | default

db_status

Sticky + active profile, host, SELECT 1

db_list_databases

List databases on active (or one-shot) profile server

db_list_schemas

List user schemas

db_list_tables

List tables/views in a schema

db_describe_table

Column metadata

db_query

Run SQL (read-only by default)

Profiles (no connection details in chat)

  1. Put both Dev and QA credentials in mcp.json (DBEAVER_DEV_*, DBEAVER_QA_* — or reuse PG_DEV_* / PG_QA_*).

  2. Say dbprofile=qa or dbprofile=dev — the assistant calls db_set_profile.

  3. Later tools reuse that sticky profile until you switch or the MCP process restarts.

  4. Optional one-shot: pass profile: "qa" on a single tool without changing sticky.

  5. database still 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 / VALUES

  • Set DBEAVER_ALLOW_WRITE=true (or PG_ALLOW_WRITE=true) to allow writes

  • DBEAVER_QUERY_MAX_ROWS / PG_MAX_ROWS caps returned rows; timeout via DBEAVER_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.js

Cursor 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 tools
db_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

    A4.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityStale
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with PostgreSQL databases through MCP, allowing users to explore database structures, inspect table schemas, and execute read-only SQL queries.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables SQL queries against PostgreSQL databases through MCP-compatible clients and includes a natural language agent for forming SQL queries from natural language.
      247
      PostgreSQL
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with PostgreSQL databases through MCP, supporting queries, DDL, DML, and schema inspection.
      35 PyPI
      6
      MIT