Dbmcp

ai.haymon由 haymon.ai 發布v0.17.0更新於 Nov 8, 2026

Database MCP server for MySQL, MariaDB, PostgreSQL & SQLite with PII redaction and write-prevention

已驗證STDIO僅桌面資料庫資料與分析

服務詳細資訊

識別碼: ai.haymon/dbmcp
傳輸: STDIO
執行環境: Desktop only
信任: Verified
發布於: Sep 16, 2026

安全提示

MCP 服務會接收對話中的工具呼叫請求，並可能執行外部操作。啟用前請先了解該服務能做什麼，並只授予它所需的權限。

註冊中心已驗證此服務的命名空間屬於 haymon.ai。它以軟體包形式執行，而不是託管端點，因此沒有可與該網域比對的端點。

SourceWeft 的檢查只涵蓋條目是否完整、端點是否回應；不審查伺服器的程式碼，也不審查其工具的行為。

在 README 中新增徽章

向讀者展示該 MCP 服務已收錄於 SourceWeft，徽章連結到本頁。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/ai.haymon%2Fdbmcp.svg)](https://sourceweft.com/mcp/ai.haymon%2Fdbmcp?utm_source=readme&utm_medium=badge)

概覽

AI 產生的概覽

讓 AI 助理連線 MySQL/MariaDB、PostgreSQL 或 SQLite 的 MCP 伺服器，可瀏覽資料庫結構、執行唯讀查詢、視需要寫入並檢視執行計畫。

可以做什麼: 列出資料庫、資料表、檢視表、觸發程序、函式、預存程序與具體化檢視，可選擇回傳詳細中繼資料並支援搜尋
執行唯讀 SQL 查詢（SELECT、SHOW、DESCRIBE、USE、EXPLAIN），結果支援游標分頁
僅在關閉唯讀模式時執行寫入查詢與 DDL，例如建立或刪除資料庫、刪除資料表
檢視查詢執行計畫，PostgreSQL 與 MySQL/MariaDB 可選擇附上 analyze 統計
可選擇對查詢輸出做 PII 去識別化，使用正規表達式規則或使用者自備的 NER 模型
適用情境: 適合讓助理梳理關聯式資料庫結構、依即時資料回答問題，或針對 MySQL、MariaDB、PostgreSQL、SQLite 撰寫並執行 SQL，包括只能經 SSH 跳板主機存取的資料庫。
執行需求: 以本機程序執行（單一執行檔或已發佈的容器映像），透過 stdio 或 HTTP 通訊。需要目標資料庫的連線設定（後端、主機、連接埠、使用者、密碼、資料庫名稱），可用 DBMCP_* 環境變數或 YAML 設定檔提供；DBMCP_TRANSPORT 為必填。HTTP 模式使用 DBMCP_HTTP_HOST 與 DBMCP_HTTP_PORT，綁定非回送位址需在 DBMCP_HTTP_AUTH_TOKEN 提供 Bearer 權杖。SSH 通道需 SSH 主機、使用者及金鑰或密碼。

安裝前請注意

資料庫憑證透過環境變數或設定檔傳入，README 的快速開始範例以明文寫入密碼。寫入工具（writeQuery、createDatabase、dropDatabase、dropTable）可修改或刪除資料；唯讀模式預設開啟，除非確實需要寫入否則應保持開啟。綁定非回送位址會把資料庫暴露給能存取該連接埠的人，Host/Origin 允許清單並非身分驗證。PII 去識別化預設關閉，且僅作用於查詢輸出。

安裝

在 SourceWeft 中

開啟儀表板中的 Dbmcp，將其新增到工作區。
為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照儲存庫中的啟動說明。

README

Database MCP

[CI] [Release] [License: MIT] [Docs]

A single-binary MCP server for SQL databases. Connect your AI assistant to MySQL/MariaDB, PostgreSQL, or SQLite with zero runtime dependencies.

Website · Documentation · Releases

[demo]

Features ✨

Multi-database — MySQL/MariaDB, PostgreSQL, and SQLite from one binary
MCP tools — schema discovery (listDatabases, listTables, listViews, listTriggers, listFunctions, listProcedures, listMaterializedViews), data access (readQuery, writeQuery), DDL (createDatabase, dropDatabase, dropTable), and explainQuery. Read-only mode hides the write tools (writeQuery, createDatabase, dropDatabase, dropTable). See MCP Tools for per-backend availability.
Single binary — ~7 MB, no Python/Node/Docker needed
Multiple transports — stdio (for Claude Desktop, Cursor) and HTTP (for remote/multi-client)
Layered config — DBMCP_* environment variables, an env file, and an optional YAML config file with ${} interpolation, with sensible defaults per backend
SSH tunnel — reach MySQL/MariaDB/PostgreSQL through an SSH bastion with an embedded client: password or key auth, known_hosts verification, automatic reconnect

Install 📦

macOS, Linux, WSL:

Windows PowerShell:

Windows CMD:

See the installation docs for Docker, Cargo, and other methods.

Quick Start 🚀

Using `.mcp.json` (recommended)

Add a .mcp.json file to your project root. MCP clients read this file and configure the server automatically.

Stdio transport — the client starts and manages the server process:

json

{  "mcpServers": {    "dbmcp": {      "command": "dbmcp",      "env": {        "DBMCP_DB_BACKEND": "mysql",        "DBMCP_DB_HOST": "127.0.0.1",        "DBMCP_DB_PORT": "3306",        "DBMCP_DB_USER": "root",        "DBMCP_DB_PASSWORD": "secret",        "DBMCP_DB_NAME": "mydb"      }    }  }}

{  "mcpServers": {    "dbmcp": {      "command": "dbmcp",      "env": {        "DBMCP_DB_BACKEND": "mysql",        "DBMCP_DB_HOST": "127.0.0.1",        "DBMCP_DB_PORT": "3306",        "DBMCP_DB_USER": "root",        "DBMCP_DB_PASSWORD": "secret",        "DBMCP_DB_NAME": "mydb"      }    }  }}

HTTP transport — you start the server yourself, the client connects to it:

bash

# Start the server firstDBMCP_TRANSPORT=http DBMCP_DB_BACKEND=mysql DBMCP_DB_USER=root DBMCP_DB_NAME=mydb dbmcp

# Start the server firstDBMCP_TRANSPORT=http DBMCP_DB_BACKEND=mysql DBMCP_DB_USER=root DBMCP_DB_NAME=mydb dbmcp

json

{  "mcpServers": {    "dbmcp": {      "type": "http",      "url": "http://127.0.0.1:9001/mcp"    }  }}

{  "mcpServers": {    "dbmcp": {      "type": "http",      "url": "http://127.0.0.1:9001/mcp"    }  }}

Note: The "type": "http" field is required for HTTP transport. Without it, clients like Claude Code will reject the config.

To require a bearer token, start the server with DBMCP_HTTP_AUTH_TOKEN and send it from the client:

bash

DBMCP_HTTP_AUTH_TOKEN="$(openssl rand -hex 32)" DBMCP_TRANSPORT=http DBMCP_DB_BACKEND=mysql DBMCP_DB_USER=root DBMCP_DB_NAME=mydb dbmcp

DBMCP_HTTP_AUTH_TOKEN="$(openssl rand -hex 32)" DBMCP_TRANSPORT=http DBMCP_DB_BACKEND=mysql DBMCP_DB_USER=root DBMCP_DB_NAME=mydb dbmcp

json

{  "mcpServers": {    "dbmcp": {      "type": "http",      "url": "http://127.0.0.1:9001/mcp",      "headers": { "Authorization": "Bearer ${DBMCP_TOKEN}" }    }  }}

{  "mcpServers": {    "dbmcp": {      "type": "http",      "url": "http://127.0.0.1:9001/mcp",      "headers": { "Authorization": "Bearer ${DBMCP_TOKEN}" }    }  }}

Using environment variables

bash

# MySQL/MariaDBDBMCP_DB_BACKEND=mysql DBMCP_DB_HOST=localhost DBMCP_DB_USER=root DBMCP_DB_NAME=mydb dbmcp
# PostgreSQLDBMCP_DB_BACKEND=postgres DBMCP_DB_HOST=localhost DBMCP_DB_USER=postgres DBMCP_DB_NAME=mydb dbmcp
# SQLiteDBMCP_DB_BACKEND=sqlite DBMCP_DB_NAME=./data.db dbmcp
# PostgreSQL through an SSH bastion (DB host is resolved by the bastion)DBMCP_DB_BACKEND=postgres DBMCP_DB_HOST=db.internal DBMCP_DB_USER=postgres DBMCP_DB_NAME=mydb \DBMCP_SSH_HOST=bastion.example.com DBMCP_SSH_USER=deploy DBMCP_SSH_KEY=~/.ssh/id_ed25519 dbmcp
# HTTP transport (loopback only, no token required)DBMCP_TRANSPORT=http DBMCP_DB_BACKEND=mysql DBMCP_DB_USER=root DBMCP_DB_NAME=mydb dbmcp
# HTTP transport on all interfaces — a bearer token is REQUIREDDBMCP_HTTP_AUTH_TOKEN=change-me DBMCP_TRANSPORT=http DBMCP_HTTP_HOST=0.0.0.0 \DBMCP_DB_BACKEND=mysql DBMCP_DB_USER=root DBMCP_DB_NAME=mydb dbmcp

# MySQL/MariaDBDBMCP_DB_BACKEND=mysql DBMCP_DB_HOST=localhost DBMCP_DB_USER=root DBMCP_DB_NAME=mydb dbmcp
# PostgreSQLDBMCP_DB_BACKEND=postgres DBMCP_DB_HOST=localhost DBMCP_DB_USER=postgres DBMCP_DB_NAME=mydb dbmcp
# SQLiteDBMCP_DB_BACKEND=sqlite DBMCP_DB_NAME=./data.db dbmcp
# PostgreSQL through an SSH bastion (DB host is resolved by the bastion)DBMCP_DB_BACKEND=postgres DBMCP_DB_HOST=db.internal DBMCP_DB_USER=postgres DBMCP_DB_NAME=mydb \DBMCP_SSH_HOST=bastion.example.com DBMCP_SSH_USER=deploy DBMCP_SSH_KEY=~/.ssh/id_ed25519 dbmcp
# HTTP transport (loopback only, no token required)DBMCP_TRANSPORT=http DBMCP_DB_BACKEND=mysql DBMCP_DB_USER=root DBMCP_DB_NAME=mydb dbmcp
# HTTP transport on all interfaces — a bearer token is REQUIREDDBMCP_HTTP_AUTH_TOKEN=change-me DBMCP_TRANSPORT=http DBMCP_HTTP_HOST=0.0.0.0 \DBMCP_DB_BACKEND=mysql DBMCP_DB_USER=root DBMCP_DB_NAME=mydb dbmcp

Warning: Binding a non-loopback address (e.g. DBMCP_HTTP_HOST=0.0.0.0) exposes the database to anyone who can reach the port. dbmcp refuses to start in that case unless DBMCP_HTTP_AUTH_TOKEN is set. The Host/Origin allowlists protect against browser DNS rebinding only — they are not authentication.

Using a config file

yaml

# dbmcp.yamldatabase:  backend: postgres  host: localhost  user: postgres  password: ${DB_PASSWORD:?set DB_PASSWORD}  name: mydb

# dbmcp.yamldatabase:  backend: postgres  host: localhost  user: postgres  password: ${DB_PASSWORD:?set DB_PASSWORD}  name: mydb

From an MCP client, pass "args": ["--config-file", "~/path/to/dbmcp.yaml"] or an absolute path; relative paths resolve against the process working directory, which the client controls. See Config File.

Configuration ⚙️

Every setting has a DBMCP_* environment variable and a YAML key. Each setting is resolved with clear precedence:

process environment > env files (--env-file) > config files (--config-file) > defaults

Environment variables are typically set by your MCP client (via env or envFile in the server config). An empty DBMCP_* value counts as unset. Nothing is discovered automatically: a file is read only when you name it.

Flag	Env Variable	Description
`--config-file <PATH>`	`DBMCP_CONFIG_FILE`	YAML config file (`${}` interpolation, strict keys); repeatable (env var: comma list), later wins
`--env-file <PATH>`	`DBMCP_ENV_FILE`	Env file of `KEY=VALUE` lines; repeatable (env var: comma list), later wins

Layer files by repeating a flag, e.g. a shared base plus local overrides: dbmcp --config-file base.yaml --config-file local.yaml. Each setting comes from the last file that sets it; lists replace.

There are no per-setting flags. Booleans accept true/false, 1/0, t/f (not yes/no); lists are comma-separated in env vars.

Configuration reference — every setting with its YAML key, env var, type, and default, plus Migrating from CLI flags
Config File — file schema, ${} interpolation, env file format, path resolution, Docker, and error output

Security note: Read-only mode is on by default (DBMCP_DB_READ_ONLY=true). The default HTTP Origin allowlist accepts browser pages from any port on localhost/127.0.0.1/[::1]; on shared or development machines, set DBMCP_HTTP_AUTH_TOKEN or narrow DBMCP_HTTP_ALLOWED_ORIGINS to the explicit origins you trust (e.g. http://localhost:5173).

The SSH tunnel is MySQL/MariaDB/PostgreSQL only and uses an embedded SSH client (no ssh binary). DBMCP_DB_HOST/DBMCP_DB_PORT are resolved by the SSH server. With both a key and a password set, the key is tried first. See SSH Tunnel for host-key policies, limitations, and troubleshooting.

MCP Tools 🧩

listDatabases

Lists accessible databases, paginated via cursor / nextCursor. See Cursor Pagination for iteration details. Not available for SQLite.

listTables

Lists tables in a database, paginated via cursor / nextCursor. See Cursor Pagination for iteration details.

Parameters: database (defaults to the active database; SQLite has no database parameter), cursor, search, detailed.

search is an optional case-insensitive LIKE/ILIKE pattern with % (any sequence) and _ (single character) as wildcards — pass users% to match names beginning with users, or %order% for substring matching. A bare word with no wildcards matches only an exact table name.