Dbmcp

ai.haymonPublished by haymon.aiv0.16.0Updated Nov 4, 2026

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

VerifiedSTDIODesktop onlyDatabases Developer Tools

Server details

Identifier: ai.haymon/dbmcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to haymon.ai. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![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)

Overview

AI-generated overview

MCP server that connects an AI assistant to MySQL/MariaDB, PostgreSQL or SQLite for schema discovery, read queries, optional writes, and query plans.

What you can do: List databases, tables, views, triggers, functions, procedures and materialized views, with optional detailed metadata and search
Run read-only SQL queries (SELECT, SHOW, DESCRIBE, USE, EXPLAIN) with cursor pagination
Run write queries and DDL such as creating or dropping databases and tables, only when read-only mode is disabled
Explain query plans, optionally with analyze statistics on PostgreSQL and MySQL/MariaDB
Optionally redact PII in query output using regex rules or a user-supplied NER model
When to use it: Useful when you want an assistant to explore a relational schema, answer questions from live data, or draft and run SQL against MySQL, MariaDB, PostgreSQL or SQLite, including databases reachable only through an SSH bastion.
Requirements: Runs as a local process (single binary, or the published container image) over stdio or HTTP. Needs connection settings for the target database (backend, host, port, user, password, database name) via DBMCP_* environment variables or a YAML config file; DBMCP_TRANSPORT is required. HTTP mode uses DBMCP_HTTP_HOST and DBMCP_HTTP_PORT, and a bearer token in DBMCP_HTTP_AUTH_TOKEN for non-loopback binds. SSH tunnels need SSH host, user and key or password.

Before you install

Database credentials are passed through environment variables or config files, and the README's quick-start examples put a password in plain text. Write tools (writeQuery, createDatabase, dropDatabase, dropTable) can change or delete data; read-only mode is on by default, so keep it unless writes are intended. Binding a non-loopback address exposes the database, and the Host/Origin allowlists are not authentication. PII redaction is off by default and only covers query output.

Installation

In SourceWeft

Open Dbmcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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.