A server application designed on top of MCP to interact with Cursor and MySQL.
Mysql MCP server exists for a simple reason — assistants are far more useful when they can act on Mysql directly instead of describing what you should do. A server application designed on top of MCP to interact with Cursor and MySQL.
A -->|Request specific tool execution| B B -->|Call the corresponding executor| C[Executors]
Once Mysql is connected, these are the calls the assistant has available:
Explanation — Each file under mysql_mcp_server/executors represents a single toolTools — Executors that perform database operationsLanguage — PythonDatabase — MySQL 8.0mcp — Implements Model Context Protocol for AI communicationPyMySQL — Connects to MySQL and executes queriespandas — Processes and analyzes datapython-dotenv — Manages environment variablesfire — Implements command-line interfacesPorts — 8081 (MCP Server), 3306 (MySQL)MySQLMCPServer — Main server class that initializes and runs the MCP serverDatabaseManager — Singleton pattern-based database connection managerSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
You will need one environment variable: MYSQL_HOST. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Mysql's toolset — Explanation, Tools, Language and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Mineru98; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Explanation | Each file under mysql_mcp_server/executors represents a single tool. |
| Tools | Executors that perform database operations |
| Language | Python |
| Database | MySQL 8.0 |
| mcp | Implements Model Context Protocol for AI communication |
| PyMySQL | Connects to MySQL and executes queries |
| pandas | Processes and analyzes data |
| python-dotenv | Manages environment variables |
| fire | Implements command-line interfaces |
| Ports | 8081 (MCP Server), 3306 (MySQL) |
| MySQLMCPServer | Main server class that initializes and runs the MCP server |
| DatabaseManager | Singleton pattern-based database connection manager |
| Executors | Collection of tools for database operations |
| execute_create_table | Creates tables |
| Variable | Description | Required |
|---|---|---|
| MYSQL_HOST | Endpoint or connection string the server talks to. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.