Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y [email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
MYSQL_LEGACY_HOST=<value> MYSQL_LEGACY_USER=<value> MYSQL_LEGACY_PASSWORD=<secret> MYSQL_LEGACY_PORT=<value> MYSQL_LEGACY_DATABASE=<value> MYSQL_LEGACY_HIDE_SYSTEM_DATABASES=<value> MYSQL_LEGACY_QUERY_TIMEOUT=<value> MYSQL_LEGACY_MAX_ROWS=<value> MYSQL_LEGACY_MAX_RESULT_BYTES=<value> MYSQL_LEGACY_CONNECT_TIMEOUT=<value> MYSQL_LEGACY_POOL_SIZE=<value> MYSQL_LEGACY_ALLOW_INSERT=<value> MYSQL_LEGACY_ALLOW_UPDATE=<value> MYSQL_LEGACY_ALLOW_DELETE=<value> MYSQL_LEGACY_ALLOW_DDL=<value> MYSQL_LEGACY_DISABLE_READ_ONLY_TRANSACTIONS=<value> claude mcp add io.github.rufflet-mysql-legacy-mcp -- npx -y mysql-legacy-mcp@0.2.1รันในเทอร์มินัล
{ "mcpServers": { "io.github.rufflet-mysql-legacy-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "MYSQL_LEGACY_HOST": "<value>", "MYSQL_LEGACY_USER": "<value>", "MYSQL_LEGACY_PASSWORD": "<secret>", "MYSQL_LEGACY_PORT": "<value>", "MYSQL_LEGACY_DATABASE": "<value>", "MYSQL_LEGACY_HIDE_SYSTEM_DATABASES": "<value>", "MYSQL_LEGACY_QUERY_TIMEOUT": "<value>", "MYSQL_LEGACY_MAX_ROWS": "<value>", "MYSQL_LEGACY_MAX_RESULT_BYTES": "<value>", "MYSQL_LEGACY_CONNECT_TIMEOUT": "<value>", "MYSQL_LEGACY_POOL_SIZE": "<value>", "MYSQL_LEGACY_ALLOW_INSERT": "<value>", "MYSQL_LEGACY_ALLOW_UPDATE": "<value>", "MYSQL_LEGACY_ALLOW_DELETE": "<value>", "MYSQL_LEGACY_ALLOW_DDL": "<value>", "MYSQL_LEGACY_DISABLE_READ_ONLY_TRANSACTIONS": "<value>" } } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิด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.
information_schema fields.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.
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.
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 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
{
"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.
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.
This is a compatibility distinction, not a benchmark: choose the modern server for its modern-database features.
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 inspectionMYSQL_LEGACY_ALLOW_* flag; UPDATE and DELETE always require a WHERE clauseMYSQL_LEGACY_POOL_SIZE); no reliance on CTEs, JSON functions, or modern metadata columnsThis 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.
See CONTRIBUTING.md for how to propose changes, run checks locally, and what evidence a compatibility claim needs. Quick start:
npm ci
npm run check
npm run smoke:static
For authorized database testing, see the smoke-test instructions in the compatibility audit.
MIT.
Inspect and query MySQL 5.0–5.6; opt-in INSERT/UPDATE/DELETE/DDL. Live-verified 5.0–8.0.
{ "mcpServers": { "io.github.rufflet-mysql-legacy-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "MYSQL_LEGACY_HOST": "<value>", "MYSQL_LEGACY_USER": "<value>", "MYSQL_LEGACY_PASSWORD": "<secret>", "MYSQL_LEGACY_PORT": "<value>", "MYSQL_LEGACY_DATABASE": "<value>", "MYSQL_LEGACY_HIDE_SYSTEM_DATABASES": "<value>", "MYSQL_LEGACY_QUERY_TIMEOUT": "<value>", "MYSQL_LEGACY_MAX_ROWS": "<value>", "MYSQL_LEGACY_MAX_RESULT_BYTES": "<value>", "MYSQL_LEGACY_CONNECT_TIMEOUT": "<value>", "MYSQL_LEGACY_POOL_SIZE": "<value>", "MYSQL_LEGACY_ALLOW_INSERT": "<value>", "MYSQL_LEGACY_ALLOW_UPDATE": "<value>", "MYSQL_LEGACY_ALLOW_DELETE": "<value>", "MYSQL_LEGACY_ALLOW_DDL": "<value>", "MYSQL_LEGACY_DISABLE_READ_ONLY_TRANSACTIONS": "<value>" } } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ผู้เผยแพร่ระบุตัวแปรสภาพแวดล้อมเหล่านี้: MYSQL_LEGACY_HOST, MYSQL_LEGACY_USER, MYSQL_LEGACY_PASSWORD, MYSQL_LEGACY_PORT, MYSQL_LEGACY_DATABASE, MYSQL_LEGACY_HIDE_SYSTEM_DATABASES, MYSQL_LEGACY_QUERY_TIMEOUT, MYSQL_LEGACY_MAX_ROWS, MYSQL_LEGACY_MAX_RESULT_BYTES, MYSQL_LEGACY_CONNECT_TIMEOUT, MYSQL_LEGACY_POOL_SIZE, MYSQL_LEGACY_ALLOW_INSERT, MYSQL_LEGACY_ALLOW_UPDATE, MYSQL_LEGACY_ALLOW_DELETE, MYSQL_LEGACY_ALLOW_DDL, MYSQL_LEGACY_DISABLE_READ_ONLY_TRANSACTIONS
MySQL Legacy MCP ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-09 Inspect and query MySQL 5.0–5.6; opt-in INSERT/UPDATE/DELETE/DDL. Live-verified 5.0–8.0.