MySQL Ops MCP Server

MySQL MCP server: browse schema, query, CRUD. Delete/drop gated by user approval.

Local serverstdio

What is the MySQL Ops MCP MCP server?

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.

What you get

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.

  • 🗄️ Schema browsing: list databases, list tables, describe table structure, full table info (indexes, DDL, stats)
  • 🔍 Queries: run SELECT queries against any database
  • ✏️ CRUD: create tables, insert, update — with SQL-statement validation per tool
  • 🔐 Approval-gated destructive ops: delete_data and drop_table always require explicit user confirmation in the client
  • 🔌 Zero install: runs via npx, configured entirely through environment variables

Setting it up

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.

Configuration and credentials

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.

Choosing this one

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.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mysql ops mcp mcp server does with a few real requests.

How to install the MySQL Ops MCP MCP server

{
  "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.

Configuration

VariableDescriptionRequired
DB_HOSTEndpoint or connection string the server talks to.Optional
DB_PORTConfiguration value read at startup.Optional
DB_USERConfiguration value read at startup.Optional
DB_PASSWORDConfiguration value read at startup.Optional
DB_DATABASEConfiguration value read at startup.Optional

Frequently asked questions

It connects MySQL Ops MCP to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with MySQL Ops MCP directly.