本项目是基于MCP框架的MySQL查询服务器，支持通过SSE协议进行实时数据库操作，具备完善的安全、日志、配置和敏感信息保护机制，适用于开发、测试和生产环境下的安全MySQL数据访问。

This project is a MySQL query server based on the MCP framework, supporting real-time database operations via SSE protocol. It features comprehensive security, logging, configuration, and sensitive information protection mechanisms, suitable for secure MySQL data access in development, testing, and production environments.

• 基于FastMCP框架，异步高性能

• 支持高并发的数据库连接池，参数灵活可调

• 支持SSE实时推送

• 丰富的MySQL元数据与结构查询API

• 自动事务管理与回滚

• 多级SQL风险控制与注入防护

• 数据库隔离安全：防止跨数据库访问，支持三级访问控制

• 敏感信息自动隐藏与自定义

• 灵活的环境变量配置

• 完善的日志与错误处理

• Docker支持，快速部署

• Built on FastMCP framework, high-performance async

• Connection pool for high concurrency, with flexible parameter tuning

• SSE real-time push support

• Rich MySQL metadata & schema query APIs

• Automatic transaction management & rollback

• Multi-level SQL risk control & injection protection

• Database Isolation Security: Prevents cross-database access with 3-level access control

• Automatic and customizable sensitive info masking

• Flexible environment variable configuration

• Robust logging & error handling

• Docker support for quick deployment

# 拉取镜像
docker pull mangooer/mysql-mcp-server-sse:latest

# 运行容器
docker run -d \
  --name mysql-mcp-server-sse \
  -e HOST=0.0.0.0 \
  -e PORT=3000 \
  -e MYSQL_HOST=your_mysql_host \
  -e MYSQL_PORT=3306 \
  -e MYSQL_USER=your_mysql_user \
  -e MYSQL_PASSWORD=your_mysql_password \
  -e MYSQL_DATABASE=your_database \
  -p 3000:3000 \
  mangooer/mysql-mcp-server-sse:latest

Windows PowerShell 格式：

docker run -d `
  --name mysql-mcp-server-sse `
  -e HOST=0.0.0.0 `
  -e PORT=3000 `
  -e MYSQL_HOST=your_mysql_host `
  -e MYSQL_PORT=3306 `
  -e MYSQL_USER=your_mysql_user `
  -e MYSQL_PASSWORD=your_mysql_password `
  -e MYSQL_DATABASE=your_database `
  -p 3000:3000 `
  mangooer/mysql-mcp-server-sse:latest

pip install -r requirements.txt

复制.env.example为.env，并根据实际情况修改。 Copy .env.example to .env and modify as needed.

python -m src.server

默认监听：http://127.0.0.1:3000/sse Default endpoint: http://127.0.0.1:3000/sse

.
├── src/
│   ├── server.py           # 主服务器入口 / Main server entry
│   ├── config.py           # 配置项定义 / Config definitions
│   ├── validators.py       # 参数校验 / Parameter validation
│   ├── db/
│   │   └── mysql_operations.py # 数据库操作 / DB operations
│   ├── security/
│   │   ├── interceptor.py      # SQL拦截 / SQL interception
│   │   ├── query_limiter.py    # 风险控制 / Risk control
│   │   └── sql_analyzer.py     # SQL分析 / SQL analysis
│   └── tools/
│       ├── mysql_tool.py           # 基础查询 / Basic query
│       ├── mysql_metadata_tool.py  # 元数据查询 / Metadata query
│       ├── mysql_info_tool.py      # 信息查询 / Info query
│       ├── mysql_schema_tool.py    # 结构查询 / Schema query
│       └── metadata_base_tool.py   # 工具基类 / Tool base class
├── tests/                  # 测试 / Tests
├── .env.example            # 环境变量示例 / Env example
└── requirements.txt        # 依赖 / Requirements

注/Note: 部分云MySQL需指定DB_AUTH_PLUGIN为mysql_native_password。

本系统完全支持 MySQL 8.0 的认证机制。MySQL 8.0 默认使用 caching_sha2_password 认证插件，提供更高的安全性。

This system fully supports MySQL 8.0 authentication mechanisms. MySQL 8.0 uses caching_sha2_password by default for enhanced security.

生产环境 / Production（推荐 / Recommended）：

DB_AUTH_PLUGIN=caching_sha2_password

开发环境 / Development（简化配置 / Simplified）：

DB_AUTH_PLUGIN=mysql_native_password

使用 caching_sha2_password 时需要安装 cryptography 包（已包含在 requirements.txt 中）：

When using caching_sha2_password, the cryptography package is required (already included in requirements.txt):

pip install cryptography

本系统提供强大的数据库隔离功能，防止跨数据库访问，确保数据安全。

This system provides robust database isolation features to prevent cross-database access and ensure data security.

# Docker 启用严格模式 / Docker with strict mode
docker run -d \
  -e MYSQL_DATABASE=your_database \
  -e ENABLE_DATABASE_ISOLATION=true \
  -e DATABASE_ACCESS_LEVEL=strict \
  mangooer/mysql-mcp-server-sse:latest

# 生产环境自动启用 / Auto-enable in production
docker run -d \
  -e ENV_TYPE=production \
  -e MYSQL_DATABASE=your_database \
  mangooer/mysql-mcp-server-sse:latest

安全效果 / Security Effects：

• ✅ 阻止 SHOW DATABASES / Blocks SHOW DATABASES
• ✅ 阻止 SELECT * FROM mysql.user / Blocks SELECT * FROM mysql.user
• ✅ 阻止 SHOW TABLES FROM other_db / Blocks SHOW TABLES FROM other_db
• ✅ 允许当前数据库操作 / Allows current database operations

🔒 重要：生产环境(ENV_TYPE=production)会自动启用数据库隔离，使用 restricted 模式。

🔒 Important: Production environment (ENV_TYPE=production) automatically enables database isolation with restricted mode.

• 所有MySQL相关API工具均采用自动注册机制：
  • 无需手动在主入口维护注册代码，新增/删除工具只需在src/tools/目录下实现register_xxx_tool(s)函数即可。
  • 系统启动时自动扫描并注册，极大提升可维护性和扩展性。
• All MySQL-related API tools are registered automatically:
  • No need to manually maintain registration code in the main entry. To add or remove a tool, simply implement a register_xxx_tool(s) function in the src/tools/ directory.
  • The system scans and registers tools automatically at startup, greatly improving maintainability and extensibility.

• 连接池采用事件循环隔离与自动回收机制：
  • 每个事件循环独立池，支持高并发与多环境。
  • 定期（默认每5分钟）自动回收无效或失效的连接池，防止资源泄漏。
  • 事件循环关闭时自动关闭对应连接池，确保资源彻底释放。
  • 支持多数据库/多租户场景扩展。
• 所有资源管理操作均有详细日志，便于追踪和排查。
• The connection pool uses event loop isolation and auto-recycling:
  • Each event loop has its own pool, supporting high concurrency and multi-environment deployment.
  • Unused or invalid pools are automatically recycled every 5 minutes (by default), preventing resource leaks.
  • When an event loop is closed, its pool is automatically closed to ensure complete resource release.
  • Ready for multi-database/multi-tenant scenarios.
• All resource management operations are logged in detail for easy tracking and troubleshooting.

• 多级SQL风险等级（LOW/MEDIUM/HIGH/CRITICAL）

• SQL注入与危险操作拦截

• WHERE子句强制检查

• 数据库隔离安全：三级访问控制（strict/restricted/permissive）

• 跨数据库访问防护：阻止未授权的数据库访问

• 敏感信息自动隐藏（支持自定义字段）

• 生产环境默认只允许低风险操作

• 生产环境自动启用数据库隔离

• Multi-level SQL risk levels (LOW/MEDIUM/HIGH/CRITICAL)

• SQL injection & dangerous operation interception

• Mandatory WHERE clause check

• Database Isolation Security: 3-level access control (strict/restricted/permissive)

• Cross-database Access Protection: Blocks unauthorized database access

• Automatic sensitive info masking (customizable fields)

• Production allows only low-risk operations by default

• Auto-enable database isolation in production

• 日志级别可配置（LOG_LEVEL）

• 控制台与文件日志输出

• 详细记录运行状态与错误

• 完善的异常捕获与事务回滚

• Configurable log level (LOG_LEVEL)

• Console & file log output

• Detailed running status & error logs

• Robust exception capture & transaction rollback

A: 检查是否有WHERE条件，无WHERE为高风险，需在ALLOWED_RISK_LEVELS中允许CRITICAL。

Q: Why does DELETE not work? A: Check for WHERE clause. DELETE without WHERE is high risk (CRITICAL), must be allowed in ALLOWED_RISK_LEVELS.

A: 设置SENSITIVE_INFO_FIELDS，如SENSITIVE_INFO_FIELDS=password,token

Q: How to customize sensitive fields? A: Set SENSITIVE_INFO_FIELDS, e.g. SENSITIVE_INFO_FIELDS=password,token

A: 设置ENABLE_DATABASE_ISOLATION=true和DATABASE_ACCESS_LEVEL=strict，或使用ENV_TYPE=production自动启用。

Q: How to enable database isolation? A: Set ENABLE_DATABASE_ISOLATION=true and DATABASE_ACCESS_LEVEL=strict, or use ENV_TYPE=production for auto-enable.

A: strict模式禁止系统表访问，可改为restricted模式，或检查是否确实需要系统表访问权限。

Q: Cannot query system tables after enabling database isolation? A: strict mode blocks system table access. Use restricted mode or verify if system table access is actually needed.

A: limit必须为非负整数。

Q: limit parameter error? A: limit must be a non-negative integer.

欢迎通过Issue和Pull Request参与改进。 Contributions via Issue and Pull Request are welcome.

MIT License

本软件按"原样"提供，不提供任何形式的明示或暗示的保证，包括但不限于对适销性、特定用途的适用性和非侵权性的保证。在任何情况下，作者或版权持有人均不对任何索赔、损害或其他责任负责，无论是在合同诉讼、侵权行为还是其他方面，产生于、源于或与本软件有关，或与本软件的使用或其他交易有关。
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.