MySQL MCP Server
MySQL MCP Server is a multi-database MCP server for MySQL and 达梦 DM8 that lets AI clients inspect and run SQL against one or many configured databases, with write/delete confirmations, auditing, and a web admin page.
Execute SQL (
execute_sql) — run single SELECT / INSERT / UPDATE / DELETE / SHOW / DESCRIBE / DDL or ad-hoc statements, including cross-databasedb.tablequeries.Inspect schema (
get_schema_info) — get column names, types, nullability, defaults and comments for one table, or list all tables at once.Sample data (
get_table_sample) — fetch a few rows (default 5, max 20) to understand a table's data format.Search schema (
search_schema) — find tables/columns/comments by keyword without pulling the full schema.Switch databases by alias — one server serves many databases; each tool takes an
alias(or project folder name) or falls back to the URL?alias=/ default.Safe writes — every statement is classified 读 / 写 / 删除; writes need confirmation via an MCP elicitation popup or a one-time
confirm_token(5-min TTL, 6-second cool-down) re-submitted with the same query.Permission gates — DELETE/TRUNCATE/DROP and DDL are denied by default, toggled per alias; whole-table UPDATE/DELETE without WHERE gets an added warning; writes can optionally skip confirmation.
Auditing & errors — all write attempts (including rejections) are logged to the admin page and
logs/audit.log; real database execution failures go tologs/error_log.dbwith optional read auditing.Self-healing errors — missing-column errors return the table's actual column list, and syntax errors hint at the right quoting style (MySQL backticks / DM double quotes).
Query protection & pooling — SELECT results truncated to 500 rows, 60-second statement timeout, MySQL connection pooling by config fingerprint.
Web admin page — manage connections, users (name/account/password), export/import config, run connectivity tests, view audits and error logs; optional
ADMIN_TOKENfor LAN access.Deployment options — SSE transport with
POST /mcp?alias=Streamable HTTP, SSH tunnel reuse,.mcpbbundle for Claude Desktop, and static single-file Linux builds.
Provides tools for securely exploring and interacting with MySQL databases, including listing tables, reading table contents, executing SQL queries, retrieving schema information, sampling table data, and managing multiple database connections.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MySQL MCP Server What tables are in my database?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MySQL MCP Server
A Model Context Protocol (MCP) implementation for secure interaction with MySQL databases. This server component establishes communication between AI applications (hosts/clients) and MySQL databases, making database exploration and analysis safer and more structured through a controlled interface.
Note: MySQL MCP Server supports both STDIO (standard input/output) and Streamable HTTP (SSE) transport modes. SSE mode is recommended for remote/self-hosted deployments.
Deployment
Hosted — Fronteir AI runs the server for you; no local setup required.
Local — Smithery installs and runs the server on your own machine.
Related MCP server: mysql-mcp-server
Features
Lists available MySQL tables as resources
Reads table contents
Executes SQL queries with robust error handling
Multi-database mode (optional
MYSQL_DATABASE)SSE/HTTP transport support (
MCP_TRANSPORT=sse)SSH tunnel support
Complete table schema information
Table data sampling
Secure database access via environment variables
Comprehensive logging
Installation
Manual installation
pip install mysql-mcp-serverInstall via Smithery
Use Smithery to automatically install MySQL MCP Server for Claude Desktop:
npx -y @smithery/cli install designcomputer/mysql-mcp-server --client claudeInstall via Claude Code CLI
claude mcp add --transport stdio designcomputer-mysql_mcp_server uvx mysql_mcp_serverInstall via Autohand Code CLI
autohand mcp add mysql env MYSQL_HOST=localhost MYSQL_PORT=3306 MYSQL_USER=your_username MYSQL_PASSWORD=your_password MYSQL_DATABASE=your_database uvx mysql_mcp_serverAdding --scope project after mcp add keeps the registration in the current workspace. See Autohand Code for current CLI details.
Configuration
Set the following environment variables:
MYSQL_HOST=localhost # 数据库主机
MYSQL_PORT=3306 # 可选:数据库端口(不指定时默认 3306)
MYSQL_USER=your_username
MYSQL_PASSWORD=your_password
MYSQL_DATABASE=your_database # 可选:留空则进入多数据库模式
# 高级配置
MYSQL_SSL_MODE=DISABLED # DISABLED、REQUIRED、VERIFY_CA、VERIFY_IDENTITY
MYSQL_CONNECT_TIMEOUT=10 # 超时时间(秒)
# 连接行为(可选)
MYSQL_SQL_MODE=TRADITIONAL # 连接所应用的 SQL mode(默认:TRADITIONAL)
# 兼容性(可选)
MYSQL_CHARSET=utf8mb4
MYSQL_COLLATION=utf8mb4_unicode_ci
MYSQL_AUTH_PLUGIN= # 例如旧版 MySQL 使用 mysql_native_password
MYSQL_USE_PURE=false # 强制使用纯 Python 连接器(默认:false)
MYSQL_RAISE_ON_WARNINGS=false # 出现 SQL 警告时抛出异常(默认:false)
# SSE 传输(可选)
MCP_TRANSPORT=stdio # stdio 或 sse
MCP_SSE_HOST=0.0.0.0 # 监听所有网卡(Docker/托管部署需要)
PORT=8000 # HTTP 端口(MCP_SSE_PORT 的回退值)
MCP_SSE_ALLOWED_HOSTS= # 逗号分隔的允许 Host 头(默认:localhost:{port},127.0.0.1:{port})
# SSH 隧道(可选)
MYSQL_SSH_ENABLE=false # 设为 true 启用
MYSQL_SSH_HOST= # SSH 跳板机
MYSQL_SSH_PORT=22 # SSH 端口
MYSQL_SSH_USER= # SSH 用户名
MYSQL_SSH_KEY_PATH= # SSH 私钥路径
MYSQL_SSH_REMOTE_HOST=localhost # 从跳板机视角看的目标主机
MYSQL_SSH_REMOTE_PORT=3306
MYSQL_LOCAL_PORT=3330.env file loading
The server automatically loads the .env file via python-dotenv at startup. For local use, simply:
cp .env.example .env # 然后填入你的凭据The file is read from the process working directory (and its parent directories), so it works as expected when you start the server yourself from the project directory.
⚠️ Claude Code / Claude Desktop: these hosts start the server from their own working directories, so they cannot find the
.envin your project, and you will seeMissing required database configuration. Put theMYSQL_*values in theenvblock of your MCP configuration (see "Usage" below) instead of relying on.env.
Multi-database mode
When MYSQL_DATABASE is not set, the server enters multi-database mode:
list_resourcesreturns all user databases (system databases are filtered out)Use fully qualified table names in SQL queries, such as
mydb.mytableNote: only single SQL statements are supported; multi-statement queries are not (e.g.
USE db; SELECT ...).
Admin page and multi-database aliases (SSE mode)
Start the server in SSE mode and open the built-in admin page to manage multiple database connections, each configurable with independent read/write accounts:
# Windows PowerShell
$env:MCP_TRANSPORT="sse"; $env:MCP_SSE_PORT="8000"; python -m mysql_mcp_server
# Linux/macOS
MCP_TRANSPORT=sse MCP_SSE_PORT=8000 python -m mysql_mcp_serverAdmin page: http://127.0.0.1:8000/admin/ (loopback only — the admin API and page reject non-loopback clients and unknown Host headers; do not place it behind a reverse proxy).
Each alias can be configured:
Field | Purpose |
Connection (host/port/database) | Connection target. Leaving database empty enables multi-database mode. |
Query user (read_user) | Used for SELECT / SHOW / DESCRIBE / EXPLAIN |
Write user (write_user) | Used for DML/DDL after confirmation |
write_policy |
|
allow_delete | Master switch for DELETE / TRUNCATE / DROP (disabled by default) |
Clients connect by alias: http://127.0.0.1:8000/sse?alias=db1
(the default alias is used when alias is omitted). When config/databases.json has no entries, the original MYSQL_* environment variables still work as a backward-compatible single-database fallback (read and write share the same account in this mode).
Note the difference from Multi-database mode above: that mode exposes multiple schemas on a single connection; aliases manage multiple connections, each with independent accounts and a write policy.
How write operations are confirmed: the server classifies each statement into three levels (read / write / delete). Read operations execute directly with the query account; write and delete operations trigger an MCP elicitation dialog showing the full SQL — accepting executes it with the write account, rejecting aborts. When the client does not support elicitation, the fallback behavior follows the alias's write_policy (see table above). All write attempts are recorded in the admin page's audit list (on disk at logs/audit.log).
Available tools
execute_sql
Executes arbitrary standard SQL queries.
Arguments:
query(string)Functionality: supports
SELECT,SHOW,DESCRIBEand DML (INSERT,UPDATE,DELETE). DML operations are flagged as destructive.Limitations: only single statements are supported; multi-statement queries are not.
Cross-database: no matter what
MYSQL_DATABASEis set to, any database can be queried using thedatabase.tablesyntax.
get_schema_info
Provides detailed metadata about the database schema.
Arguments:
table_name(optional string)Output: column names, types, nullability, default values, and comments.
Cross-database: pass
database.tableto query databases other thanMYSQL_DATABASE; bare table names use the configured database.Identifier rules: names may only contain alphanumerics, underscores, and
$(a single dot is allowed as thedatabase.tableseparator).
get_table_sample
Fetches a representative data sample.
Arguments:
table_name(string),limit(optional integer, max 20)Purpose: quickly understand data format and content without pulling large result sets.
Cross-database: pass
database.tableto sample databases other thanMYSQL_DATABASE; bare table names use the configured database.Identifier rules: names may only contain alphanumerics, underscores, and
$(a single dot is allowed as thedatabase.tableseparator).
Available Prompts
In addition to tools, the server also provides MCP prompts — guided multi-step workflows that clients can launch on demand. They appear as slash commands in Claude Code (/mcp__<server>__<prompt>); in Claude Desktop they are in the prompts (+) menu.
Prompt | Arguments | Description |
| (none) | Systematically explore the database: discover available tables, inspect table schemas, sample data, and summarize contents. |
|
| Deep-dive analysis of a specified table: get its schema, sample data, and practical query suggestions. Supports |
Example (Claude Code):
/mcp__mysql__explore_database
/mcp__mysql__analyze_table customersBoth prompts orchestrate the existing get_schema_info and get_table_sample tools; explore_database also uses the resource list to enumerate tables.
Usage
With Claude Desktop
Add the following to claude_desktop_config.json:
{
"mcpServers": {
"mysql": {
"command": "uv",
"args": [
"--directory",
"path/to/mysql_mcp_server",
"run",
"mysql_mcp_server"
],
"env": {
"MYSQL_HOST": "localhost",
"MYSQL_PORT": "3306",
"MYSQL_USER": "your_username",
"MYSQL_PASSWORD": "your_password",
"MYSQL_DATABASE": "your_database"
}
}
}
}See MCP_USECASES.md for more detailed examples and agent-specific guides.
With Visual Studio Code
Add the following to mcp.json:
{
"mcpServers": {
"mysql": {
"type": "stdio",
"command": "uvx",
"args": [
"--from",
"mysql-mcp-server",
"mysql_mcp_server"
],
"env": {
"MYSQL_HOST": "localhost",
"MYSQL_PORT": "3306",
"MYSQL_USER": "your_username",
"MYSQL_PASSWORD": "your_password",
"MYSQL_DATABASE": "your_database"
}
}
}
}Note: uv must be installed first.
Debugging with MCP Inspector
MySQL MCP Server is not designed to run standalone or to be launched directly from the Python command line, but you can debug it using MCP Inspector.
MCP Inspector provides a convenient way to test and debug MCP implementations:
# 安装依赖
pip install -r requirements.txt
# 使用 MCP Inspector 调试(不要直接用 Python 运行)MySQL MCP Server is designed to be integrated into AI applications such as Claude Desktop and should not be run directly as a standalone Python program.
Development
# 克隆仓库
git clone https://github.com/designcomputer/mysql_mcp_server.git
cd mysql_mcp_server
# 创建虚拟环境
python -m venv venv
source venv/bin/activate # Windows 上用 `venv\Scripts\activate`
# 安装开发依赖
pip install -r requirements-dev.txt
# 复制示例配置并填入你的凭据
cp .env.example .env
# 编辑 .env,填入 MySQL 连接信息
# 运行测试
pytestSecurity notes
Identifier validation: table and database names passed to
get_schema_infoandget_table_sampleundergo strict whitelist validation (only alphanumerics, underscores, and$are allowed; one dot is allowed as thedatabase.tableseparator). All other special characters are rejected to prevent SQL injection.Encrypted access: full support for SSL/TLS and SSH tunnels to secure remote connections.
Log privacy: passwords and SSH private keys are automatically redacted from server logs.
Least privilege: always use dedicated MySQL users with minimal permissions.
SSE transport has no built-in authentication. The SSE server binds to
0.0.0.0by default and accepts connections without credentials. If exposed beyond localhost, place it behind a reverse proxy that enforces authentication (nginx, Caddy, Traefik). nginx + HTTP Basic Auth example:location /sse { auth_basic "MCP"; auth_basic_user_file /etc/nginx/.htpasswd; proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_buffering off; } location /messages/ { auth_basic "MCP"; auth_basic_user_file /etc/nginx/.htpasswd; proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; }Set
MCP_SSE_HOST=127.0.0.1to make the server listen only on the loopback address, making the proxy the only public entry point. SetMCP_SSE_ALLOWED_HOSTSto the public hostname forwarded by the proxy (for exampleMCP_SSE_ALLOWED_HOSTS=myserver.example.com:443).
See SECURITY.md for a complete guide to secure deployment.
Security best practices
This MCP implementation requires database access to function. To stay secure:
Create a dedicated MySQL user and grant minimal permissions
Never use root credentials or administrator accounts
Restrict database access to necessary operations
Enable logging for auditing
Regularly review database access for security
See the MySQL Security Configuration Guide for detailed instructions, including:
Creating restricted MySQL users
Setting appropriate permissions
Monitoring database access
Security best practices
⚠️ Important: always follow the principle of least privilege when configuring database access.
License
MIT License - see the LICENSE file for details.
Contributing
Fork the repository
Create a feature branch (
git checkout -b feature/amazing-feature)Commit your changes (
git commit -m 'Add some amazing feature')Push the branch (
git push origin feature/amazing-feature)Open a Pull Request
Available Tools
3 toolsexecute_sqlADestructive
Execute a SQL statement against the MySQL server. Use for SELECT, DML (INSERT/UPDATE/DELETE), SHOW, DESCRIBE, and ad-hoc queries. Supports cross-database queries using database.table notation. Single statements only — use fully qualified names instead of USE statements. Write/delete statements require user confirmation: depending on the client, either a confirmation prompt appears, or the first call returns a confirm_token — show the SQL to the user, and after explicit consent re-call with the same query plus confirm_token. Use the optional alias parameter to target a different configured database within a single connection.
Inputs: query (required), alias, confirm_token.
get_schema_infoARead-only
Get column metadata for a table or all tables in the configured database: column names, data types, nullability, default values, and comments. Call this before querying an unfamiliar table. Omit table_name to see all tables at once. Accepts bare table names (uses MYSQL_DATABASE) or database.table for cross-database lookups. Use alias to target a different configured database.
Inputs: alias, table_name.
get_table_sampleARead-only
Fetch a small sample of rows from a table to understand its data format and content. Use alongside get_schema_info before writing complex queries. Accepts bare table names (uses MYSQL_DATABASE) or database.table for cross-database lookups. Use alias to target a different configured database.
Inputs: table_name (required), alias, limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clear, distinct role: execute_sql for arbitrary SQL, get_schema_info for metadata, and get_table_sample for row previews. Although execute_sql can also run SHOW/SELECT statements, the specialized helper tools are explicitly framed as complementary, not competing.
All tool names follow a consistent verb_noun pattern in snake_case: execute_sql, get_schema_info, get_table_sample. This makes the action and target of each tool predictable.
Three tools is a compact but appropriate scope for a SQL database server: one general execution path plus two focused inspection helpers. Each tool serves a distinct need without redundancy.
The surface covers the core workflow: inspect schema, preview data, and execute arbitrary SQL for reads and writes. Cross-database behavior and user confirmation are handled, and remaining database-level operations can be reached via execute_sql.
Maintenance
Related MCP Connectors
Guard AI agents' PostgreSQL/MySQL access via MCP: SQL audit, auth, masking, write approval
Hosted MySQL MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
PostgreSQL, MySQL, and SQL Server in one session. 26 read-only MCP tools for AI agents.
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables read-only interaction with SQL databases through MCP, providing database metadata exploration, sample data retrieval, and secure query execution. Supports MySQL with multiple transport options and built-in security features including SQL injection protection and data sanitization.27 npm5MIT
- AlicenseNot gradedqualityDmaintenanceEnables MySQL database operations through MCP, including executing SQL queries, listing databases and tables, and describing table structures.5MIT
- AlicenseNot gradedqualityDmaintenanceEnables safe querying and optional writing to MySQL databases via MCP tools, with support for schema inspection, connection management, and read-only mode.16 npm3MIT
- AlicenseAqualityCmaintenanceEnables interaction with MariaDB/MySQL databases via MCP, supporting read-only mode, SQL execution, and schema inspection.6MIT