mysql-mcp-server-all
Provides read-only access to MySQL databases, allowing execution of SELECT/SHOW/DESCRIBE/EXPLAIN/WITH queries, retrieving schema information, and sampling table data.
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-all what's the schema of the users table?"
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-all
A read-only MySQL MCP server that speaks stdio, SSE, and Streamable HTTP — one binary, three transports.
Why this project exists
We needed to expose a MySQL database as an MCP server to Dify, whose "MCP (HTTP)" integration form only supports the Streamable HTTP protocol.
We evaluated the existing ecosystem:
Project | Transport | Dify "HTTP" form |
stdio; remote HTTP mode is stateless & incomplete | ❌ | |
stdio only | ❌ | |
stdio + SSE | ❌ | |
mysql-mcp-server-all (this project) | stdio + SSE + Streamable HTTP | ✅ |
This project is a derived / enhanced work of designcomputer/mysql_mcp_server (MIT). It keeps the same familiar toolset and adds the missing transport — so the same server can serve Claude Code / opencode over stdio, Cherry Studio over SSE, and Dify over Streamable HTTP.
Related MCP server: mysql-mcp
Features
Three transports via
MCP_TRANSPORT:stdio(default) /sse/streamable-httpRead-only by design: only
SELECT / SHOW / DESCRIBE / EXPLAIN / WITHSingle & multi database mode: omit
MYSQL_DATABASEto query any schema viadb.tableIdentifier whitelist against SQL injection in schema/sample tools
Optional Bearer-token auth for Streamable HTTP (recommended when binding beyond loopback)
Works from Dify, Cherry Studio, Claude Code, opencode and any MCP client
Install
Requires Python 3.10+.
# via uv (recommended)
uvx --from mysql-mcp-server-all mysql-mcp-server-all
# or pip
pip install mysql-mcp-server-allNote: this repository is GitHub-only for now. The PyPI name
mysql-mcp-server-allis reserved for future publishing.
Quick start
# stdio (Claude Code / opencode / Cherry Studio local)
MYSQL_HOST=127.0.0.1 MYSQL_USER=root MYSQL_PASSWORD=secret \
MYSQL_DATABASE=my_db mysql-mcp-server-all
# Streamable HTTP (Dify) with token auth
MYSQL_HOST=127.0.0.1 MYSQL_USER=root MYSQL_PASSWORD=secret \
MYSQL_DATABASE=my_db MCP_TRANSPORT=streamable-http \
MCP_HTTP_HOST=127.0.0.1 MCP_HTTP_PORT=8000 MCP_HTTP_TOKEN=my-token \
mysql-mcp-server-all
# -> http://127.0.0.1:8000/mcpEnvironment variables
Variable | Default | Description |
| (required) | Database host |
|
| Database port |
| (required) | Database user |
| `` | Database password |
| (none) | Default database. Omit → multi-database mode |
|
| Connection timeout (seconds) |
|
|
|
|
| Listen host for |
|
| Listen port for |
| (none) | Bearer token for |
Transports
Transport | Endpoint | Clients |
| — | Claude Code, opencode, Cursor |
|
| Cherry Studio (SSE), Claude Desktop |
|
| Dify (HTTP), Cherry Studio (HTTP) |
Client configuration
Dify (recommended: Streamable HTTP)
MCP type: HTTP
Endpoint URL: http://127.0.0.1:8000/mcp
Auth header: Authorization: Bearer <MCP_HTTP_TOKEN> (if set)
Dynamic client registration: leave disabledDify self-hosted in Docker: use
http://host.docker.internal:8000/mcp, bindMCP_HTTP_HOST=0.0.0.0, and add the target to Dify's SSRF proxy allowlist (SSRF_PROXY_ALLOW_PRIVATE_IPS/SSRF_PROXY_ALLOW_PRIVATE_DOMAINSin Dify'sdocker/.env) — Dify blocks private networks by default.
Cherry Studio
Type: SSE → URL http://127.0.0.1:8000/sse
or HTTP → URL http://127.0.0.1:8000/mcp (streamable-http)Claude Code / opencode (stdio)
{
"mcpServers": {
"mysql": {
"command": "mysql-mcp-server-all",
"env": {
"MYSQL_HOST": "127.0.0.1",
"MYSQL_USER": "root",
"MYSQL_PASSWORD": "secret",
"MYSQL_DATABASE": "my_db"
}
}
}
}opencode: use
"environment"(not"env") inopencode.json.
Tools
Tool | Arguments | Description |
|
| Run a read-only SQL query (SELECT/SHOW/DESCRIBE/EXPLAIN/WITH). Single statement. Returns JSON rows |
|
| Column metadata (SHOW FULL COLUMNS). Accepts |
|
| Sample rows from a table. Accepts |
Security
Read-only enforced in
execute_sql— write/DDL queries are rejectedIdentifier whitelist — only alphanumeric,
_,$, and one.separatorBind loopback by default (
127.0.0.1)Use a least-privilege MySQL user — never
rootwith full grantsAdd token auth (
MCP_HTTP_TOKEN) whenever you bind0.0.0.0SSE transport has no built-in auth — keep it behind a loopback or a reverse proxy with auth (nginx / Caddy)
Credits & License
Derived from designcomputer/mysql_mcp_server (MIT) — same toolset, extended with unified stdio/SSE/Streamable HTTP transports.
MIT License, see LICENSE.
Available Tools
3 toolsexecute_sqlA
Execute a read-only SQL query (SELECT / SHOW / DESCRIBE / EXPLAIN / WITH).
Returns rows as JSON. Single statements only.
Inputs: query (required). Returns: result
get_schema_infoB
Return column metadata (name, type, nullability, key, default) for a table.
Accepts database.table notation for cross-database lookups.
Inputs: table_name (required). Returns: result
get_table_sampleA
Fetch a representative sample of rows (max 20) from a table.
Accepts database.table notation for cross-database lookups.
Inputs: table_name (required), limit. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
The tools are largely distinct: execute_sql runs arbitrary read-only queries, get_schema_info returns column metadata, and get_table_sample fetches sample rows. However, execute_sql can also perform SELECT queries that return sample data, creating some overlap with get_table_sample.
All tool names follow a consistent verb_noun pattern in snake_case: execute_sql, get_schema_info, get_table_sample. This makes the toolset predictable and easy to navigate.
Three tools is a reasonable count for a focused read-only MySQL exploration server. While on the smaller side, each tool serves a clear purpose and the set does not feel overly thin.
The domain is well-covered for read-only database exploration: arbitrary SQL queries, schema metadata, and sample rows cover the core needs. Missing functionality like listing all tables can be achieved via execute_sql, so there are no major gaps.
Maintenance
Related MCP Connectors
Read-only MCP server for The Quiet Protocol's engines, benchmarks, proof, and business data.
Read-only MCP server for ClassQuill, a tutoring-business-management platform.
Text-to-SQL MCP server: read-only queries on PostgreSQL, MySQL and SQL Server with your real schema
An MCP server that provides read access to your cloud storage providers, bank accounts and more.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server for MySQL database operations, providing secure HTTP endpoints for read-only queries, performance analysis, and server monitoring.22MIT
- AlicenseNot gradedqualityBmaintenanceA MySQL MCP server for local stdio clients, enabling database queries and management with read-only/write modes, audit logging, and configurable security.554 npmMIT
- AlicenseNot gradedqualityDmaintenanceA secure, read-only MySQL database proxy using MCP protocol, enabling SQL queries and table inspections via HTTP.14 npm1MIT
- FlicenseAqualityCmaintenanceSecurity-hardened, read-only MySQL MCP server that enables safe, read-only access to MySQL databases for running SELECT queries, exploring schemas, and sampling data via MCP clients.9-