dsh-db-mcp

dsh-db-mcp

English | 中文

A DSH plugin that hands your databases to the agent. Register a connection once, then just ask — the agent queries it through MCP tools and answers in the conversation.

The fastest path is the one you already walked: import the connections DBeaver already knows, saved passwords included, and skip typing anything.

Three things you do not have to do

• Do not retype connections. The importer reads your DBeaver workspace (data-sources.json) and decrypts credentials-config.json with DBeaver's own key, so host, port, database, user and the saved password arrive together. Tick the boxes, click import, done. Existing endpoints are marked, so the same connection is never added twice.
• Do not configure DSH. The bundle inserts one Loader row. The plugin starts its own Python MCP server and registers the tools itself — no dsh-mcp-client row, no JSON to edit, no environment variable to export.
• Do not prepare a Python environment. No venv to create, no pip install to run by hand: the panel finds an interpreter, builds .venv and installs the driver packages from Runtime → Install / repair dependencies.

How it works, on one page

Left: what you do in the panel. Right: what happens in the conversation once a source exists.

Screenshots

The source list. A health strip across the top, sources grouped the way you grouped them, engine badges, the identifier each tool call needs, and a failed probe stays inline with its full error and a copy button. The Import from DBeaver tab sits right next to it.

One set of sources, every DSH you run

The registry lives in ~/.dsh/db-mcp/ (datasources.json + secrets.json, mode 0600), not inside a profile. So:

• Install it in the desktop app, the web UI, or both — they read the same file, so a source imported once shows up everywhere.
• Run several DSH windows at the same time. Each instance starts its own Python service; the first takes the HTTP port and the next ones step to the following free port automatically, so nothing refuses to start.
• Upgrade or reinstall without redoing the setup. Sources, groups, settings and the audit log survive; only the plugin code is replaced.

The same server, for your other agents

The panel publishes the identical MCP server over streamable HTTP. The Connect tab shows the address (http://127.0.0.1:8765/dsh-db-mcp) and writes the entry for you with one click:

Point JetBrains AI or anything else that speaks MCP at the same URL and it works too. Data sources, the read-only flag, the writable schemas and the DDL switch are shared; the audit log, the tool list and the conversation-level limit stay inside DSH. The safety page has the line-by-line table; clients.md walks through the endpoint.

Requirements

Run

dsh plugin --profile desktop add dsh-db-mcp   # desktop app
dsh plugin --profile web add dsh-db-mcp       # web UI

--profile picks the profile to install into (desktop and web ship with DSH; any other name is created on first use). Remove with dsh plugin --profile desktop remove dsh-db-mcp.

Upgrading has its own traps — pnpm's metadata cache, its release cooldown, and Windows holding the old files open. See Updating from the app; if the app asks you to disable other configurations first, restart DSH and update again (that releases the running app's hold on the bundle).

Then:

1. Sidebar → Data sources.
2. Import from DBeaver → tick the connections → Import selected.
3. Ask the agent something like "which tables does my Chinook database have?"

A connection whose password was never saved shows no password; open the source once and type it — it goes to secrets.json and never comes back to the page.

Read the full README on GitHub →