@enemyrr/mcp-mysql-server A Model Context Protocol server that provides MySQL database operations. This server. The @enemyrr/mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it rather than through you.

What it actually does

• 14 database tools — for queries, schema management, and more
• MCP Resources — for browsing database schema
• MCP Prompts — for generating SQL queries
• Multiple connection methods (URL, workspace, direct)
• Secure connection handling with automatic cleanup
• Prepared statement support for query parameters

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Configuration

You will need one environment variable: DATABASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

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. It is maintained by enemyrr; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• 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.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the @enemyrr/mcp mcp server does with a few real requests.