MySQL MCP server: browse schema, query, CRUD. Delete/drop gated by user approval.
MySQL Ops MCP MCP server exists for a simple reason — assistants are far more useful when they can act on MySQL Ops MCP directly instead of describing what you should do. MySQL MCP server: browse schema, query, CRUD. Delete/drop gated by user approval.
A MySQL database MCP Server. Let AI tools like Claude Code / Cursor / Codex talk to your MySQL databases in natural language — browse databases and tables, inspect schemas, run queries, and perform CRUD operations, with destructive operations (DELETE / DROP) gated behind explicit user approval.
The server ships on npm as npm, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
You will need 5 environment variables: DB_HOST, DB_PORT, DB_USER, DB_PASSWORD, DB_DATABASE. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by GT-dinuo; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MySQL Ops MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
{
"mcpServers": {
"mysql-ops": {
"command": "npx",
"args": ["-y", "npm"],
"env": {
"DB_HOST": "your-value",
"DB_PORT": "your-value",
"DB_USER": "your-value",
"DB_PASSWORD": "your-value",
"DB_DATABASE": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| DB_HOST | Endpoint or connection string the server talks to. | Optional |
| DB_PORT | Configuration value read at startup. | Optional |
| DB_USER | Configuration value read at startup. | Optional |
| DB_PASSWORD | Configuration value read at startup. | Optional |
| DB_DATABASE | Configuration value read at startup. | 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.