Skip to main content
hc
Submit
mcpSource-backedReview first Safety ✓ Privacy ✓

MySQL MCP Server

MCP server for connecting Claude to MySQL databases with schema inspection, SQL query execution, SSH tunnel support, multi-database mode, and configurable write-operation controls.

by benborla·added 2026-06-05·
Claude CodeClaude Desktop
HarnessClaude CodeClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Safety notes

  • MySQL MCP Server can inspect schemas and run SQL queries against configured databases.
  • Write and DDL operations can be enabled through environment variables, so keep insert, update, delete, and DDL permissions disabled unless explicitly required.
  • Use a least-privilege MySQL user and avoid connecting the server to production databases with broad grants.
  • Multi-database mode can expose every database visible to the configured MySQL user.
  • SSH tunnel settings, query timeouts, cache settings, logging, and rate limits should be reviewed before connecting an MCP client.

Privacy notes

  • Database hostnames, schema names, table names, column names, query text, query results, credentials, prompts, logs, and tool outputs may be visible to the MCP client and model provider.
  • Query results may contain customer data, credentials, tokens, personal data, financial data, internal IDs, or regulated records.
  • MCP client configs, shell history, logs, screenshots, and shared project files can leak MySQL credentials if not handled carefully.
  • Prefer local or user-scoped MCP configuration for database credentials instead of committing project-scoped configs.

Prerequisites

  • Node.js 20 or newer available to the MCP client runtime.
  • MySQL 5.7 or newer, with MySQL 8.0 or newer recommended upstream.
  • Dedicated MySQL user with only the database grants required for the intended workflow.
  • MySQL host, port, credentials, database name, SSL, and optional SSH tunnel settings prepared.
  • Insert, update, delete, DDL, multi-database, and schema-specific permissions reviewed before enabling them.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
15 minutes
Difficulty
advanced
Full copyable content
{
  "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"
      }
    }
  }
}

About this resource

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

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.

#mysql#database#sql#ssh#developer-tools

Source citations

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.