MCP-MySQL-Ops is a comprehensive MySQL database monitoring and operations tool that provides 19 specialized capabilities for database administration, performance analysis, and system health monitoring through natural language queries. Key capabilities include: - Performance monitoring using MySQL's Performance Schema for query analytics, slow query identification, and execution statistics. - Schema and structure discovery with detailed table, index, and column analysis across multiple databases. - Real-time connection and process monitoring to diagnose locks, connection issues, and active operations. - Storage engine intelligence with InnoDB status monitoring and table optimization recommendations. - Storage analysis and capacity planning with table size metrics and growth insights. - User and configuration exploration for database security and settings review. Compatible with MySQL 5.7+, MySQL 8.0+, AWS RDS, and Aurora MySQL. Operates in read-only mode for production safety.

MCP Server for MySQL Operations and Monitoring

[](https://opensource.org/licenses/MIT)

[](https://smithery.ai/server/@call518/mcp-mysql-ops) [](https://www.buymeacoffee.com/call518)

[](https://github.com/call518/MCP-MySQL-Ops/actions/workflows/pypi-publish.yml)

---

Architecture & Internal (DeepWiki)

[](https://deepwiki.com/call518/MCP-MySQL-Ops)

---

Overview

You are working with the MCP MySQL Operations Server, a powerful tool that provides comprehensive MySQL database monitoring and analysis capabilities through natural language queries. This server offers 19 specialized tools for database administration, performance monitoring, and system analysis. Leverages MySQL's Performance Schema and Information Schema for deep insights into database operations and performance metrics.

---

Features

🔧 Advanced Capabilities

Tool Usage Examples

---

---

---

⭐ Quickstart (5 minutes)

> Note: The mysql container included in docker-compose.yml is intended for quickstart testing purposes only. You can connect to your own MySQL instance by adjusting the environment variables as needed.

> If you want to use your own MySQL instance instead of the built-in test container: > - Update the target MySQL connection information in your .env file (see MYSQL_HOST, MYSQL_PORT, MYSQL_USER, MYSQL_PASSWORD, MYSQL_DATABASE). > - In docker-compose.yml, comment out (disable) the mysql and mysql-init-data containers to avoid starting the built-in test database.

Flow Diagram of Quickstart/Tutorial

1. Environment Setup

> Note: The system automatically handles user permissions - both root users and regular users are supported with appropriate access control.

git clone https://github.com/call518/MCP-MySQL-Ops.git
cd MCP-MySQL-Ops
Copy and check environment configuration
cp .env.example .env

Default configuration (works out-of-the-box):

#### MySQL Root Configuration for Docker:
MYSQL_ROOT_HOST=%
MYSQL_ROOT_PASSWORD=changeme!@34
#### MySQL Host Configuration:
MYSQL_HOST=host.docker.internal
MYSQL_PORT=13306
MYSQL_USER=root
MYSQL_PASSWORD=${MYSQL_PASSWORD}
MYSQL_DATABASE=test_ecommerce

For your own MySQL server:

# Edit .env file with your MySQL connection details
MYSQL_HOST=your-mysql-server.com
MYSQL_PORT=3306
MYSQL_USER=your_username     # Will auto-grant permissions on test DBs
MYSQL_PASSWORD=your_password
MYSQL_DATABASE=your_default_db
Then disable built-in containers in docker-compose.yml
Comment out: mysql and mysql-init-data services

> Note: The MySQL container is configured with proper volume