Skip to main content
Glama
MySQL MCP Server

MySQL MCP Server


MySQL MCP Server

A Model Context Protocol (MCP) server for MySQL databases, built with NestJS and MCP-Nest. Enables AI assistants like Claude and Cursor to interact with MySQL databases through a standardized protocol.

English · 繁體中文


Overview

MySQL MCP Server exposes MySQL database operations as MCP tools, allowing AI assistants to:

  • Query and explore database schemas

  • Execute SQL queries with permission controls

  • List tables, describe table structures, and browse databases

  • Run in multiple transport modes (stdio, HTTP SSE, Streamable HTTP)

Related MCP server: MCP MySQL Server

Features

Description

Connection Pool

Efficient MySQL connection management with configurable pool size

Permission Control

Granular SQL operation permissions (SELECT, INSERT, UPDATE, DELETE, DDL)

DRY_RUN Mode

Validate SQL queries without returning actual data

MCP Tools

Standardized database operations exposed via Model Context Protocol

Graceful Shutdown

Clean resource cleanup on process termination

File Logging

Configurable log output with rotation support

Prerequisites

  • Node.js 18+

  • MySQL 5.7+ database

  • npm or pnpm package manager

Installation

# Global installation (recommended)
npm install -g @johnson.lee/mysql-mcp-server

# Or use npx
npx @johnson.lee/mysql-mcp-server

Quick Start

# Set environment variables
export DB_HOST=localhost
export DB_PORT=3306
export DB_USER=root
export DB_PASSWORD=your_password
export DB_NAME=your_database

# Run the server
mysql-mcp

Configuration

Configure via environment variables:

Database Connection

Variable

Default

Description

DB_HOST

localhost

MySQL host

DB_PORT

3306

MySQL port

DB_USER

root

MySQL user

DB_PASSWORD

-

MySQL password

DB_NAME

test_db

Database name

DB_POOL_MIN

2

Min pool connections

DB_POOL_MAX

10

Max pool connections

Permission Control

Variable

Default

Description

ALLOW_SELECT

true

Allow SELECT queries

ALLOW_VIEW

true

Allow SHOW / DESCRIBE

ALLOW_INSERT

false

Allow INSERT

ALLOW_UPDATE

false

Allow UPDATE

ALLOW_DELETE

false

Allow DELETE

ALLOW_DDL

false

Allow CREATE/ALTER/DROP/TRUNCATE

Server Options

Variable

Default

Description

MCP_SERVER_NAME

mysql-mcp-server

Server name — used as log file prefix

MCP_TRANSPORT

stdio

Transport: stdio/http-sse/streamable-http

LOG_LEVEL

info

Log level: debug/info/warn/error

LOG_DIR

./logs

Log directory

DRY_RUN

false

Validate SQL without returning data

Editor Integration

Claude Desktop

Edit ~/.config/claude/claude_desktop_config.json:

{
  "mcpServers": {
    "mysql": {
      "command": "npx",
      "args": ["@johnson.lee/mysql-mcp-server"],
      "env": {
        "DB_HOST": "localhost",
        "DB_USER": "root",
        "DB_PASSWORD": "your_password",
        "DB_NAME": "your_database"
      }
    }
  }
}

Cursor

Create .cursor/mcp.json:

{
  "mcpServers": {
    "mysql": {
      "command": "npx",
      "args": ["@johnson.lee/mysql-mcp-server"],
      "env": {
        "DB_HOST": "localhost",
        "DB_USER": "root",
        "DB_PASSWORD": "your_password",
        "DB_NAME": "your_database"
      }
    }
  }
}

Multi-Environment Setup

You can register multiple instances to connect different databases simultaneously. Each instance should have a unique MCP_SERVER_NAME, which is also used as the log file prefix — e.g. dev-info.log, prod-error.log.

Note: All env values must be strings. Use "true" / "false", not bare booleans.

{
  "mcpServers": {
    "dev-mysql": {
      "command": "npx",
      "args": ["@johnson.lee/mysql-mcp-server"],
      "env": {
        "MCP_SERVER_NAME": "dev",
        "DB_HOST": "dev-db.example.com",
        "DB_PORT": "3306",
        "DB_USER": "dev_user",
        "DB_PASSWORD": "dev_password",
        "DB_NAME": "dev_db",
        "LOG_DIR": "/tmp/mcp-logs"
      }
    },
    "prod-mysql": {
      "command": "npx",
      "args": ["@johnson.lee/mysql-mcp-server"],
      "env": {
        "MCP_SERVER_NAME": "prod",
        "DB_HOST": "prod-db.example.com",
        "DB_PORT": "3306",
        "DB_USER": "prod_user",
        "DB_PASSWORD": "prod_password",
        "DB_NAME": "prod_db",
        "LOG_DIR": "/tmp/mcp-logs",
        "DRY_RUN": "true"
      }
    }
  }
}

With the above config, log files are written to LOG_DIR with the server name as prefix:

/tmp/mcp-logs/
├── dev-info.log
├── dev-error.log
├── prod-info.log
└── prod-error.log

Available Tools

list_tables

List all tables in the current database.

describe_table

Get table structure (columns, types, keys, etc.).

{
  "name": "describe_table",
  "arguments": { "tableName": "users" }
}

execute_query

Execute SQL queries.

{
  "name": "execute_query",
  "arguments": { "sql": "SELECT * FROM users LIMIT 10" }
}

list_databases

List all available databases on the MySQL server.


Built with NestJS and MCP-Nest

Available Tools

4 tools
describe_tableB

Get the structure of a specific table

Inputs: tableName (required).

execute_queryB

Execute a SELECT query on the database

Inputs: sql (required), timeout.

list_databasesA

List all available databases

Inputs: no named parameters.

list_tablesA

List all tables in the current database

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: table structure, SELECT query execution, database listing, and table listing. There is no overlap in functionality.

    Naming Consistency5/5

    All tool names consistently follow the verb_noun pattern (list_databases, list_tables, describe_table, execute_query), making them easy to parse and select.

    Tool Count4/5

    With 4 tools, the set is minimal but focused. It covers basic database exploration needs, though one might expect additional tools for write operations or schema browsing.

    Completeness3/5

    The set handles core read operations (listing, describing, querying) but lacks any write capabilities (INSERT, UPDATE, DELETE) and does not support non-SELECT queries, leaving notable gaps for a general MySQL server.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A server that enables AI models to interact with MySQL databases through a Model Control Protocol, providing tools for table creation, schema inspection, query execution, and data retrieval.
      28
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI models to interact with MySQL databases, providing tools for querying, executing statements, listing tables, and describing table structures.
      5
      290 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI models to interact with MySQL databases through a standardized interface, providing tools for querying, executing commands, and managing database schemas.
      7
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI models to interact with MySQL databases through natural language, supporting SQL queries, table creation, and schema exploration.
      3
      -