MySQL Legacy MCP

io.github.RuffletPublished by GitHub account Ruffletv0.2.1Updated Oct 24, 2026

Inspect and query MySQL 5.0–5.6; opt-in INSERT/UPDATE/DELETE/DDL. Live-verified 5.0–8.0.

VerifiedSTDIODesktop onlyDatabasesDeveloper Tools

Overview

AI-generated overview

Local stdio MCP server that lets an assistant inspect and query legacy MySQL 5.0–5.6 databases, read-only by default with opt-in write tools.

What you can do
  • Check the server version and list databases, tables and views
  • Inspect schema details: columns, CREATE TABLE statements and indexes
  • Run a single parsed SELECT with row and result-size limits, wrapped in a read-only transaction on MySQL 5.6.5+
  • Optionally run one INSERT, UPDATE, DELETE or table-level DDL statement, each gated by its own allow flag
When to use it
Use it when an assistant needs to explore a MySQL 5.0, 5.1, 5.5 or 5.6 database, for example to understand a legacy schema or prepare a migration, and when modern MySQL servers that assume 5.7+ features do not work. Write access can be enabled per statement type when needed.
Requirements
Runs locally over stdio via npx, so Node.js 18.14.1 or later and npm are needed. Requires a MySQL host, user and password (MYSQL_LEGACY_HOST, MYSQL_LEGACY_USER, MYSQL_LEGACY_PASSWORD), ideally a dedicated account with only the needed read and metadata privileges; port, default database and limits are optional. No TLS or custom charset options.
Before you install
The password is passed as the MYSQL_LEGACY_PASSWORD environment variable, so keep it out of shared configs. Write tools are off by default; enabling MYSQL_LEGACY_ALLOW_INSERT, MYSQL_LEGACY_ALLOW_UPDATE, MYSQL_LEGACY_ALLOW_DELETE or MYSQL_LEGACY_ALLOW_DDL lets the assistant change or delete data and alter tables, and UPDATE/DELETE only require a WHERE clause. MySQL 8.0 default authentication is unsupported, and TLS, custom charsets and pre-4.1 old_password are not covered.

Installation

In SourceWeft

  1. Open MySQL Legacy MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

MySQL Legacy MCP

[CI] [npm] [License: MIT] [Glama] [Indexed on TensorBlock MCP Index]

MCP server for legacy MySQL 5.0–5.6 databases through stdio. The package is on npm as mysql-legacy-mcp and in the official MCP Registry as io.github.Rufflet/mysql-legacy-mcp.

It uses MySQL 5.1-compatible SQL and SHOW metadata queries. Live MCP tests cover MySQL 5.0.51a, 5.1.73, 5.5.62, and 5.6.51. It is deliberately small: read-only by default, with INSERT/UPDATE/DELETE/DDL as opt-in tools disabled unless explicitly enabled; no TLS configuration, and no custom authentication or charset options.

Is this for you?

  • You need an AI agent to inspect a MySQL 5.0, 5.1, 5.5, or 5.6 database.
  • Your current MySQL MCP server assumes MySQL 5.7+, JSON functions, or newer information_schema fields.
  • You need schema inspection and SELECT queries, with write operations off by default and opt-in per statement type.

If you are seeing ER_NOT_SUPPORTED_AUTH_MODE, HANDSHAKE_INSECURE_AUTH, Old password authentication is not supported, legacy TLS errors, or garbled cp1251 / latin1 text, read Troubleshooting first. Those symptoms are not all solved by this package.

Requirements

  • Node.js 18.14.1 or later
  • npm
  • A dedicated MySQL account with only the required read and metadata privileges

Where it is listed

Installation is always local stdio via npm (npx -y mysql-legacy-mcp). Directory pages do not make that faster; they are discovery indexes. The official MCP Registry is the machine-readable source (io.github.Rufflet/mysql-legacy-mcp) that aggregators ingest, including env-var metadata from server.json. Clients that speak that registry can pre-fill configuration from it.

Maintainer submission status for other directories is in docs/RELEASE_CHECKLIST.md.

Quick install

Claude Code

sh
claude mcp add --transport stdio mysql-legacy \  --env MYSQL_LEGACY_HOST=127.0.0.1 \  --env MYSQL_LEGACY_USER=legacy_reader \  --env MYSQL_LEGACY_PASSWORD=replace-with-a-secret \  --env MYSQL_LEGACY_DATABASE=legacy_app \  -- npx -y mysql-legacy-mcp

Codex

sh
codex mcp add mysql-legacy \  --env MYSQL_LEGACY_HOST=127.0.0.1 \  --env MYSQL_LEGACY_USER=legacy_reader \  --env MYSQL_LEGACY_PASSWORD=replace-with-a-secret \  --env MYSQL_LEGACY_DATABASE=legacy_app \  -- npx -y mysql-legacy-mcp

Cursor and other clients

json
{  "mcpServers": {    "mysql-legacy": {      "type": "stdio",      "command": "npx",      "args": ["-y", "mysql-legacy-mcp"],      "env": {        "MYSQL_LEGACY_HOST": "127.0.0.1",        "MYSQL_LEGACY_USER": "legacy_reader",        "MYSQL_LEGACY_PASSWORD": "replace-with-a-secret",        "MYSQL_LEGACY_DATABASE": "legacy_app"      }    }  }}

Use the schema required by your client. Full copy-paste instructions for Claude Desktop, Codex, VS Code, Windsurf, Gemini, Trae, Qoder, and more are in the Installation guide.

Compatibility

MySQLStatus
5.0Verified: 5.0.51a
5.1Verified: 5.1.73
5.5Verified: 5.5.62
5.6Verified: 5.6.51
5.7Verified reference only: 5.7.44
8.0Not a target; default caching_sha2_password is unsupported

Each tested target passed all 11 tools — the 7 read-only tools plus the 4 opt-in write tools, with MYSQL_LEGACY_ALLOW_* flags checked both left at their default false and explicitly enabled — through a real MCP stdio session. On MySQL 5.6.5 and later, this also exercised the actual START TRANSACTION READ ONLY path used by mysql_legacy_select; below that version it exercised the silent plain-query fallback. Exact sources, test conditions, and the MySQL 8.0 boundary are recorded in the compatibility audit. This does not cover pre-4.1 old_password, custom connection charsets, TLS, or your server's exact patch level.

Compared with modern MySQL MCP servers

ServerStated MySQL baselineFocus
mysql-legacy-mcpVerified live: 5.0–5.6Legacy schema inspection and SELECT by default; opt-in INSERT/UPDATE/DELETE/DDL, with UPDATE/DELETE always requiring a WHERE clause
@benborla29/mcp-server-mysql5.7+; 8.0+ recommendedModern MySQL features such as TLS, SSH tunnels, and optional writes

This is a compatibility distinction, not a benchmark: choose the modern server for its modern-database features.

Features

  • Read-only SELECT tool with parser checks and result-size limits, wrapped in a read-only transaction on MySQL 5.6.5+
  • SHOW-based database, table, column, CREATE TABLE, and index inspection
  • Opt-in INSERT/UPDATE/DELETE/DDL tools, each disabled by default and gated by its own MYSQL_LEGACY_ALLOW_* flag; UPDATE and DELETE always require a WHERE clause
  • A small pooled set of MySQL connections (MYSQL_LEGACY_POOL_SIZE); no reliance on CTEs, JSON functions, or modern metadata columns

Tools

ToolPurpose
mysql_legacy_pingReturn VERSION()
mysql_legacy_selectRun one parsed SELECT statement
mysql_legacy_insertRun one INSERT statement (opt-in, MYSQL_LEGACY_ALLOW_INSERT)
mysql_legacy_updateRun one UPDATE statement with a required WHERE clause (opt-in, MYSQL_LEGACY_ALLOW_UPDATE)
mysql_legacy_deleteRun one DELETE statement with a required WHERE clause (opt-in, MYSQL_LEGACY_ALLOW_DELETE)
mysql_legacy_ddlRun one table-level CREATE/ALTER/DROP/TRUNCATE/RENAME statement (opt-in, MYSQL_LEGACY_ALLOW_DDL)
mysql_legacy_list_databasesList databases
mysql_legacy_list_tablesList tables and views
mysql_legacy_describe_tableShow columns
mysql_legacy_show_create_tableShow table DDL
mysql_legacy_list_indexesShow indexes

Documentation

Why this exists

This project came from a QA/fullstack workflow that needed AI-assisted inspection of a production MySQL 5.1 database. It is a focused utility for exploring legacy schemas and preparing migrations.

Contributing

See CONTRIBUTING.md for how to propose changes, run checks locally, and what evidence a compatibility claim needs. Quick start:

sh
npm cinpm run checknpm run smoke:static

For authorized database testing, see the smoke-test instructions in the compatibility audit.

License

MIT.

Source: README.md at commit 24be335

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts