Summary
Schema, indexes and plan — the three things a slow query needs.
Running SQL alone leaves an assistant guessing about why something is slow. Having the index list and the EXPLAIN plan alongside the schema means an answer about performance can point at a missing index instead of speculating. Running as a container keeps the credentials out of your client's configuration.
What it is
A MySQL access server that runs as a Docker container beside your database. The client connects to it over a local HTTP endpoint, and the database credentials stay in the container's environment.
What you get
- Every table in the connected database, listed
- A table's schema read back
- Arbitrary SQL executed
- The indexes on a table
- The EXPLAIN plan for a query
- A health check, for confirming the connection before anything depends on it
Requirements
A reachable MySQL database and its host, port, user, password and database name in the container's environment. Docker, or Python with Poetry if you would rather run it directly.
Setup effort
One command plus a key — uvx mysql-mcp, then supply credentials