Skip to main content
Glama
zhengyun1008

MCP Server for MySQL

by zhengyun1008
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

MCP Server for MySQL based on NodeJS

Demo

A Model Context Protocol server that provides access to MySQL databases with fine-grained access control. Supports multiple databases, access modes, and table-level permissions.

Features

  • Multi-database support: Connect to multiple MySQL databases simultaneously

  • Access control: readonly, readwrite, full modes per database

  • Table-level permissions: Whitelist/blacklist with wildcards and regex

  • Read-only transaction protection: Database-level safety for readonly mode

  • Backward compatible: Works with single database environment variables

Related MCP server: MySQL MCP Server

Components

Tools

Tool

Description

mysql_query

Read-only SELECT queries (always available)

mysql_execute

Write operations (only visible when writable databases exist)

Resources

  • mysql://connections: List of database connections with access modes

  • mysql://{db}/tables/{table}/schema: Table schema

Prompts

  • mysql_usage_guide: Dynamic guide based on configured databases

Configuration

Config File

Create ~/.mcp_mysql/databases.json:

{
  "databases": [
    {
      "name": "prod",
      "host": "prod-db.example.com",
      "port": 3306,
      "user": "readonly_user",
      "password": "***",
      "database": "production",
      "accessMode": "readonly"
    },
    {
      "name": "dev",
      "host": "localhost",
      "port": 3306,
      "user": "dev_user",
      "password": "***",
      "database": "development",
      "accessMode": "readwrite",
      "allowedTables": ["log_*", "tmp_*", "/^test_.*/i"]
    }
  ]
}

Access Modes

Mode

SELECT

INSERT/UPDATE/DELETE

DDL

readonly (default)

✅

❌

❌

readwrite

✅

✅

❌

full

✅

✅

✅

Table Patterns

Format

Example

Matches

Exact

log_table

Only log_table

Wildcard

log_*

log_ prefix

Regex

/^test_\d+$/i

test_ + digits

Environment Variables

Variable

Description

MYSQL_CONFIG_PATH

Custom config file path

MYSQL_HOST

Legacy single-database host

MYSQL_PORT

Legacy single-database port

MYSQL_USER

Legacy single-database user

MYSQL_PASS

Legacy single-database password

MYSQL_DB

Legacy single-database name

Usage with Claude Desktop

Multi-database configuration (Recommended)

First, create ~/.mcp_mysql/databases.json with your database configurations.

Then add to your claude_desktop_config.json:

{
  "mcpServers": {
    "mcp_server_mysql": {
      "command": "npx",
      "args": [
        "-y",
        "@zhengyun1008/mcp-server-mysql"
      ]
    }
  }
}

Single database (Legacy, backward compatible)

{
  "mcpServers": {
    "mcp_server_mysql": {
      "command": "npx",
      "args": [
        "-y",
        "@zhengyun1008/mcp-server-mysql"
      ],
      "env": {
        "MYSQL_HOST": "127.0.0.1",
        "MYSQL_PORT": "3306",
        "MYSQL_USER": "root",
        "MYSQL_PASS": "",
        "MYSQL_DB": "db_name"
      }
    }
  }
}

Usage Examples

User: "查询 prod 库中的用户表"
→ mysql_query(database="prod", sql="SELECT * FROM users")

User: "在 dev 库的 log_test 表插入一条记录"
→ mysql_execute(database="dev", sql="INSERT INTO log_test ...", confirm=true)

Security

  • readonly mode: Uses SET SESSION TRANSACTION READ ONLY for database-level protection

  • SQL validation: Validates statement type before execution

  • Table validation: Checks whitelist/blacklist before write operations

  • Confirmation required: Write operations require confirm=true

Troubleshooting

If you encounter an error "Could not connect to MCP server mcp-server-mysql", you may need to explicitly set the path of all required binaries such as the configuration below:

{
  "mcpServers": {
    "mcp_server_mysql": {
      "command": "/path/to/npx/binary/npx",
      "args": [
        "-y",
        "@zhengyun1008/mcp-server-mysql"
      ],
      "env": {
        "MYSQL_HOST": "127.0.0.1",
        "MYSQL_PORT": "3306",
        "MYSQL_USER": "root",
        "MYSQL_PASS": "",
        "MYSQL_DB": "db_name",
        "PATH": "/path/to/node/bin:/usr/bin:/bin"
      }
    }
  }
}

License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.

Available Tools

1 tool
mysql_queryA

Run a read-only SELECT query on a MySQL database

ParametersJSON Schema
NameRequiredDescriptionDefault
databaseNoDatabase connection name. Available:
sqlYesSELECT query to execute (read-only)

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool is 'read-only', which implies non-destructive behavior and safety for data retrieval. However, it lacks details on authentication needs, rate limits, error handling, or response format, leaving gaps in behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the key information ('Run a read-only SELECT query') without any wasted words. It is appropriately sized for the tool's complexity and structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is incomplete for a database query tool. It covers the basic purpose and read-only nature but lacks details on return values, error conditions, or operational constraints, which are important for effective tool use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, so the schema already documents both parameters ('database' and 'sql') adequately. The description adds minimal value by reinforcing that the 'sql' parameter must be a 'SELECT query (read-only)', but does not provide additional syntax or format details beyond what the schema specifies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Run a read-only SELECT query') and the resource ('on a MySQL database'). It distinguishes this as a read-only query execution tool with no siblings to differentiate from, making the purpose explicit and complete.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by specifying 'read-only SELECT query', which suggests it should be used for data retrieval rather than modifications. However, it does not provide explicit guidance on when to use this tool versus alternatives (e.g., for write operations or other database types), as there are no sibling tools mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.6/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clearly defined purpose for running read-only SELECT queries.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'mysql_query' follows a clear and descriptive pattern.

Tool Count2/5

A single tool is too few for a MySQL server, as it severely limits functionality. The scope suggests a database server, but with only read-only queries, it lacks essential operations like INSERT, UPDATE, DELETE, or schema management.

Completeness1/5

The tool surface is severely incomplete for a MySQL server. It only supports read-only SELECT queries, missing all other CRUD operations, data manipulation, schema changes, and administrative tasks, which will cause significant agent failures.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • MySQL MCP Server

    wenjiachengy
    A
    license
    B
    quality
    Not graded
    maintenance
    Enables secure interaction with MySQL databases through listing tables, reading data, and executing SQL queries with proper error handling and controlled access.
    1

  • MySQL MCP Server

    ddonathan
    F
    license
    Not graded
    quality
    Not graded
    maintenance
    Enables direct interaction with MySQL databases through SQL queries, table exploration, and schema inspection with support for prepared statements and connection pooling.

  • MySQL MCP Server

    GuangYiDing
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables interaction with MySQL databases through connection management, SQL execution, and schema exploration. It features multi-connection support and a safety-focused 'dangerous mode' for write operations.
    41
    4
    MIT

  • Text-to-SQL MCP Server

    down530
    F
    license
    Not graded
    quality
    C
    maintenance
    Enables secure SQL query execution on MySQL databases with authentication and permission control, allowing users to explore database tables and run read-only queries.

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zhengyun1008/mcp-server-mysql'

If you have feedback or need assistance with the MCP directory API, please join our Discord server