MySQL MCP Server

Content

MySQL MCP Server connects Claude-compatible MCP clients to MySQL databases. It can inspect schema resources, execute SQL queries, work through SSH tunnels, support multi-database mode, and enforce configurable insert, update, delete, and DDL permissions.

The upstream README documents the @benborla29/mcp-server-mysql NPM package, Claude Code and Codex CLI configuration, global install and NPX usage, SSH tunnel setup, multi-database mode, and environment-variable based operation controls.

Source Review

• https://github.com/benborla/mcp-server-mysql
• https://github.com/benborla/mcp-server-mysql/blob/main/README.md
• https://github.com/benborla/mcp-server-mysql/blob/main/package.json
• https://github.com/benborla/mcp-server-mysql/blob/main/README-MULTI-DB.md
• https://registry.npmjs.org/%40benborla29%2Fmcp-server-mysql

These sources were reviewed on 2026-06-05. Prefer the live repository, README, multi-database guide, package metadata, and NPM registry metadata for current package name, environment variables, write-permission controls, and SSH tunnel behavior.

Features

• Inspect MySQL schemas and database connections.
• Execute SQL queries through an MCP tool surface.
• Disable insert, update, delete, and DDL operations by default through environment variables.
• Configure schema-specific permissions for multi-database workflows.
• Use MySQL host/port, socket, SSL, SSH tunnel, query timeout, cache, and rate-limit settings.
• Run in single-database mode or multi-database mode.
• Install globally or run with NPX from MCP clients such as Claude Code and Codex CLI.

Installation

For MCP clients that launch stdio servers:

{
  "mcpServers": {
    "mysql": {
      "command": "npx",
      "args": ["-y", "@benborla29/mcp-server-mysql"],
      "env": {
        "MYSQL_HOST": "127.0.0.1",
        "MYSQL_PORT": "3306",
        "MYSQL_USER": "YOUR_MYSQL_USER",
        "MYSQL_PASS": "YOUR_MYSQL_PASSWORD",
        "MYSQL_DB": "YOUR_DATABASE",
        "ALLOW_INSERT_OPERATION": "false",
        "ALLOW_UPDATE_OPERATION": "false",
        "ALLOW_DELETE_OPERATION": "false",
        "ALLOW_DDL_OPERATION": "false"
      }
    }
  }
}

Restart the MCP client after adding the server and verify the configured MySQL user has only the grants needed for the intended workflow.

Use Cases

• Ask Claude to inspect tables and columns before writing application code.
• Query development data while debugging a local feature.
• Review schema shape across one database or several databases.
• Use SSH tunnels for remote development databases.
• Keep production schemas read-only while allowing write operations in development or test schemas.
• Add explicit DDL controls before asking an agent to help with migrations.

Safety and Privacy

Database MCP tools need careful boundaries. Even when write operations are disabled in the MCP server configuration, the configured MySQL user should also use least-privilege database grants. Do not rely on a single layer of MCP-side configuration to protect production data.

Keep credentials out of project-scoped files unless the project is private and the credentials are placeholders. Review logs, shell history, client config, and screenshots for leaked MySQL passwords, hostnames, schema names, and query results.

Duplicate Check

No benborla/mcp-server-mysql entry, @benborla29/mcp-server-mysql package entry, or matching source URL was found in content/mcp.

• Source repositorygithub.com 2026-07-21T07:17:01+00:00
• Documentationgithub.com
• Submitted by oktofeesh12026-06-05