← Back to directory

io.github.t8y2/dbx

Official

Query and manage 70+ databases from AI agents via connections already configured in DBX

GitHub source repository ↗

★ 13.3k Stars Category · Database Very popular

57FMRS · C

Reliability

8/20

Security and permissions

10/20

Maintenance

14/20

Documentation

13/20

Setup experience

12/20

DBX is an actively maintained, Apache-2.0 licensed open-source project recognized on Trendshift, HelloGitHub, and Product Hunt. Its MCP server ships as a separate Rust-backed npm package with configurable read-only/read-write/full-access modes, but it depends on database connections already configured in DBX, and enabling write access requires the operator to independently assess the data risk.

Read the FMRS scoring method →

DBX is a 20 MB cross-platform database client supporting MySQL, PostgreSQL, SQLite, Redis, MongoDB, DuckDB, SQL Server, Dameng, and 70+ other databases. Its MCP Server is a separate Rust-powered npm package (@dbx-app/mcp-server) that runs over stdio, letting AI coding agents such as Claude Code, Cursor, and Windsurf reuse database connections already set up in DBX's desktop, web, or Docker deployments to list connections, browse tables, execute SQL, and open tables directly in DBX's UI. The MCP server is distributed independently from the desktop application, so installing DBX does not automatically install the MCP executable.

Tools

The tool list has not been reviewed yet.

Setup

Make sure DBX (desktop, web, or Docker) is installed and has at least one database connection already configured.
Add the server to your .mcp.json: run via npx -y @dbx-app/mcp-server (stdio transport), or download a precompiled native binary for your platform from GitHub Releases (no Node.js required).
In DBX Settings → MCP, manage the connection allowlist and choose an access mode: Read only (read_only), Data read/write (safe_write), or Full access (high_risk_write).
For DBX Web or Docker deployments, set DBX_WEB_URL to point at the web backend API; if the web login requires a password, also set DBX_WEB_PASSWORD.
On Windows portable builds, set DBX_DATA_DIR in the MCP config to the data directory next to DBX.exe (the folder containing dbx.db).

claude_desktop_config.json

{"mcpServers": {"dbx": {"command": "npx", "args": ["-y", "@dbx-app/mcp-server"]}}}

Generate and validate client config

Fit and risk

Best for

Developers already using DBX desktop, web, or Docker with connections configured
Teams working across many different database engines who want one consistent MCP access point
Users who want a lightweight (20 MB) client without Java or Python runtime dependencies

Not for

Users without an existing DBX installation or configured connections, since the MCP server itself does not manage new database credentials — it relies on connections already set up in DBX
Users who specifically need an MCP server maintained by a database vendor (e.g. the MySQL, PostgreSQL, or MongoDB projects themselves) rather than DBX's own client wrapper
Environments with strict no-write automation requirements where operators cannot verify the current DBX centralized MCP access-mode policy

Required permissions

Access to database connection credentials already configured in DBX
Ability to execute SQL according to the mode selected in DBX Settings → MCP (read_only / safe_write / high_risk_write)
DBX_WEB_URL (and DBX_WEB_PASSWORD if password login is enabled) for Web/Docker deployments
DBX_DATA_DIR pointing to the data directory containing dbx.db for Windows portable builds
Node.js >= 18 when run via npx (or use the Node-free precompiled native binary instead)

Risks and side effects

If the access mode is set to Data read/write or Full access, the AI agent can modify or delete data in connected databases
Insufficiently reviewed AI-generated SQL could execute unintended write operations against production databases
The legacy DBX_MCP_ALLOW_WRITES=0 environment variable only enforces read-only behavior until a central MCP policy has been saved for the first time — after that it no longer applies, so operators must track policy state
DBX_WEB_PASSWORD is stored in plaintext in client configuration, so config files should be protected

Troubleshooting

Confirm DBX itself is installed and has at least one configured database connection — the MCP server is distributed separately and is not auto-installed with the DBX app
If launching via npx fails, verify Node.js >= 18 is installed, or switch to a precompiled native binary from GitHub Releases
On Windows portable builds, if data isn't found, check that DBX_DATA_DIR is set and points to the data directory next to DBX.exe containing dbx.db
If connecting to a Web/Docker DBX backend fails, verify DBX_WEB_URL is correct and that DBX_WEB_PASSWORD matches the web login password when one is required
If write operations are unexpectedly allowed or blocked, check the access mode (read_only / safe_write / high_risk_write) and connection allowlist in DBX Settings → MCP

Use cases

Query and browse databases already configured in DBX directly from Claude Code, Cursor, Windsurf, or other MCP-compatible editors without switching tools

Have an AI agent list available connections, browse table schemas, run SQL, and jump straight to the matching table in DBX's UI

Perform exploratory queries and lightweight data operations across a multi-database environment covering 70+ engines through one consistent MCP entry point

Supported clients

Claude CodeFull support

CursorFull support

WindsurfFull support

Related MCP servers

Compare with other MCP servers