Labsco
MCP SERVER

MySQL Server Pro

by wenb1n-dev

MySQL with the DBA side attached: health checks, lock analysis, index usage, and three permission roles deciding what SQL may run.

Relational SQL Databases
Summary
The questions you ask when the database is slow.

Most MySQL servers stop at running a query. Lock analysis, index usage and a running-health check are what you actually reach for at two in the morning, and here they are calls rather than half-remembered SQL.

What it is

An MCP server for MySQL that goes past CRUD. Alongside SQL execution it reports database health, table locks and index usage, and it gates what can run through three roles — readonly, writer and admin.

What you get
  • SQL executed under a role that decides which statement types are permitted
  • Several statements in one call, separated by semicolons
  • Table names and fields found from their Chinese table comments
  • Table structure and index definitions read
  • Table lock analysis
  • Health checks for the running database and for index usage
  • Chinese field names converted to pinyin initials
  • STDIO, SSE and Streamable HTTP transports, with OAuth available for authentication
Requirements

A MySQL instance and a role setting: readonly permits SELECT, SHOW, DESCRIBE and EXPLAIN; writer adds INSERT, UPDATE and DELETE; admin adds CREATE, ALTER, DROP and TRUNCATE.

Setup effort

One command plus a key — pip install mysql_mcp_server_pro, then supply credentials