mysql-mcp

Query MySQL tables from Claude Code — read-only by default.

An MCP server that gives Claude Code (and any MCP client) read access to a MySQL database through structured, parameterized query tools. No raw SQL passthrough by default — the tool surface is designed so the worst possible outcome is a SELECT that returns too many rows.

Modeled on Agent360's browser-mcp (same MCP server patterns: stdio transport, lifecycle handling, LLM-facing tool descriptions).

Testing

npm test

Three layers, all under node --test (no test framework dependency):

Integration env (defaults match the local Docker dev setup; override freely):

TEST_DB_HOST / TEST_DB_PORT / TEST_DB_USER / TEST_DB_PASSWORD / TEST_DB_NAME
TEST_DB_RW_USER / TEST_DB_RW_PASSWORD   → write suite (skipped if unset)
TEST_DB_ADMIN_PASSWORD                  → cleanup of write-test rows

Related MCP server: mysql-mcp

Status — M5

Five read tools plus two opt-in write tools, all integration-tested against a real MySQL:

Writing — opt-in at two levels

Write tools exist only when both hold:

1. Server: started with ALLOW_WRITES=1 — otherwise the tools are not even advertised in tools/list, and dispatch refuses them anyway.

2. Database: the connected account holds INSERT/UPDATE grants (verify with check_permissions).

Safety defaults on update_rows: where is required (a where-less UPDATE is rejected — the classic footgun), limit defaults to 1 and caps at 100. Every write reads the affected rows back and returns the verified new state.

Security — three tiers, all enforced

Every tool call is audited to stderr — shape only (tool, table name, row count), never values. Same secret-hygiene contract as browser-mcp's action log.

Reliability & LLM experience

• Errors are LLM-actionable. Raw MySQL/network errors are classified and shipped with a hint that says what to do next: Error: Table 'x' doesn't exist → Hint: Call list_tables..., Unknown column → Hint: Call describe_table..., connection failures → Hint: Check DB_HOST / DB_PORT... (marked retryable).

• Retry policy. Transient connection failures retry once automatically (SELECTs are idempotent); SQL errors never retry. Same read-only/retryable split as browser-mcp's CDP whitelist.

• Result truncation. Results are capped at 50,000 serialized chars (on top of the 200-row cap). When truncated, the response carries truncated: true, fetched, and a hint telling the model to narrow (WHERE filters, fewer columns, offset paging) instead of re-querying bigger.

Roadmap

• ✅ M1–M6 core done: skeleton, query tools, security, reliability, opt-in writes, test suite

• ⏸️ npm publishing — skipped by decision; add @scope name, LICENSE, registry metadata (server.json / glama.json) if you ever publish

Install (local — no npm publish needed)

cd /path/to/mysql-mcp
node bin/cli.js install

This writes the mysql-mcp server into ~/.claude/mcp.json, pointing at this checkout's index.js by absolute path (dev-mode install, same pattern as browser-mcp's install.sh). Credentials use ${VAR} placeholders — Claude Code resolves them from your environment, never stored in the config file:

{
  "mcpServers": {
    "mysql-mcp": {
      "command": "node",
      "args": ["/path/to/mysql-mcp/index.js"],
      "env": {
        "DB_HOST": "${DB_HOST}",
        "DB_PORT": "${DB_PORT}",
        "DB_USER": "${DB_USER}",
        "DB_PASSWORD": "${DB_PASSWORD}",
        "DB_NAME": "${DB_NAME}"
      }
    }
  }
}

Database account — read-only, always

CREATE USER 'mcp_ro'@'%' IDENTIFIED BY '<strong-password>';
GRANT SELECT ON <your_db>.* TO 'mcp_ro'@'%';

Point it at a read replica if you have one.

Dev

npm ci
node index.js    # → [mysql-mcp] MySQL MCP server running (stdio)

Environment variables

License

MIT