MySQL MCP Server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track Python package and MySQL-driver changes affecting database access

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

AI-assisted MySQL exploration and controlled SQL access.

What we know

A MySQL MCP for schema inspection, table sampling and single-statement SQL over stdio or remote transports.

Maintenance / activity evidence

Observed Aug 2, 2026 (UTC)docs: add Autohand Code MCP setup ( 93)

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Configured MySQL grants. Writes: INSERT; UPDATE; DELETE.
MySQL credentials; optional SSH key
Sensitive access: Database contents, Credentials, SSH connectivity

The server can read and mutate MySQL data; use a least-privilege account and restrict remote transport exposure.

Security source · repository notice ↗Security source · policy file ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

1,398 repository stars

Stars observed Oct 6, 2026.

Registry availability was inconsistent during the audit; 30-day downloads withheld pending recheck.

All limitations / Review context

Which MySQL connection and query features remain supported?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

The server can read and mutate MySQL data; use a least-privilege account and restrict remote transport exposure.
Configured MySQL grants.
MySQL credentials; optional SSH key
Database data/results are returned to the client.
Reviewed write actions: INSERT; UPDATE; DELETE
Sensitive access: Database contents, Credentials, SSH connectivity
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No independent runtime, installation, or comprehensive security audit was performed.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
Stable 30-day package metric
Single statements only.
INSERT, UPDATE and DELETE are supported and destructive.
Remote exposure needs host and origin controls.

Original activity observations

2026-08-02T13:36:20Z: docs: add Autohand Code MCP setup ( 93)

Technical identity

github.com/designcomputer/mysql_mcp_server

Exact implementation source: https://github.com/designcomputer/mysql_mcp_server ↗
Reviewed resource type: MCP Server
Repository identity: designcomputer/mysql_mcp_server
Package identity: pypi:mysql-mcp-server

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
designcomputer/mysql_mcp_server
Recorded repository material and project history.
Evidence source ↗
pypi.org/project/mysql-mcp-server/
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Claude Code

Publisher instructions with a documented client setup path.

Source evidence observed Oct 12, 2026.

Additional setup details required — see the specific gaps below.

Warning

MYSQL_PORT defaults to 3306 and MYSQL_DATABASE can be omitted; examples may include both optional fields.
Use read-only database credentials if only reading. Publisher supports writes; credentials should have least necessary privileges.
Use only the named client/schema. Replace illustrative credential/path placeholders with your own settings.
Claude Code removal name and Claude Desktop JSON key differ: choose the actual registered client and name; never run a client removal command for an unrelated entry.
Publisher Claude Code registration name is designcomputer-mysql_mcp_server, while its Claude Desktop sample mcpServers key is mysql; these are different registration identities.
These are not interchangeable; removing either entry does not revoke database credentials.
Exact vendor-specific credential revoke procedure not established from checked official Setup documentation; may be external or not applicable. Do not invent.
MCP100 client-scope note: this Claude Code CLI example applies only to that client and the exact registered name in the command. Desktop, Cursor and other clients use their own configuration; do not run it for a differently named entry.
publisher README config shape Replace the supplied credential/path placeholders privately; use only the named configuration schema.
MCP100 client-scope note: this Claude Code CLI example applies only to that client and the exact registered name in the command. Desktop, Cursor and other clients use their own configuration; do not run it for a differently named entry. Claude Code removal name and Claude Desktop JSON key differ: choose the actual registered client and name; never run a client removal command for an unrelated entry.

Install / connect
Publisher instructions
Publisher-specific setup path. Follow prerequisites, then register or connect to your MCP host.
claude mcp add --transport stdio designcomputer-mysql_mcp_server uvx mysql_mcp_server

Configure / authenticate

Publisher instructions

MYSQL_HOST, MYSQL_PORT, MYSQL_USER, MYSQL_PASSWORD, MYSQL_DATABASE must be supplied to child environment or host MCP config.

Advanced configuration · claude desktop json · Publisher instructions

claude desktop json · Publisher instructions

{
  "mcpServers": {
    "mysql": {
      "args": [
        "--directory",
        "path/to/mysql_mcp_server",
        "run",
        "mysql_mcp_server"
      ],
      "command": "uv",
      "env": {
        "MYSQL_DATABASE": "your_database",
        "MYSQL_HOST": "localhost",
        "MYSQL_PASSWORD": "your_password",
        "MYSQL_PORT": "3306",
        "MYSQL_USER": "your_username"
      }
    }
  }
}

Check connection
Suggested check
Use read-only schema discovery; confirm correct database target before queries.
Remove / uninstall / revoke
MCP100 setup guide
`claude mcp remove designcomputer-mysql_mcp_server` removes the registration; does not remove MySQL or tables.
MCP100 client-scope guidance: each CLI removal example targets only its named client and exact registered entry. Package names, Desktop/Cursor configuration keys and Codex/Claude registration names may differ; use the entry you actually registered. Client removal does not revoke provider credentials.
claude mcp remove designcomputer-mysql_mcp_server

Official Documentation & Sources

What it does

A MySQL MCP for schema inspection, table sampling and single-statement SQL over stdio or remote transports.

Capability: Data & Databases
Resource type: MCP Server
Best fit: AI-assisted MySQL exploration and controlled SQL access.

Representative uses

List databases and tables
Inspect schema metadata
Sample table data
Run SELECT and DML statements

Limitations

Single statements only.
INSERT, UPDATE and DELETE are supported and destructive.
Remote exposure needs host and origin controls.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: MySQL credentials; optional SSH key
Permissions: Configured MySQL grants.
Data handling: Database data/results are returned to the client.
Cost: free
Risk and cautions: The server can read and mutate MySQL data; use a least-privilege account and restrict remote transport exposure.

Access scope and cautions

Write actions: INSERT UPDATE DELETE
Sensitive access: Database contents Credentials SSH connectivity
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: List databases and tables; Inspect schema metadata; Sample table data; Run SELECT and DML statements.

What setup and authentication are documented?

Recorded installation/entrypoint step: pip install mysql-mcp-server. Recorded transport: stdio, sse, streamable_http. Recorded environment-variable notes: MYSQL_HOST; MYSQL_USER; MYSQL_PASSWORD; MYSQL_PORT; MYSQL_DATABASE; MCP_TRANSPORT; MCP_SSE_HOST; PORT; MCP_SSE_ALLOWED_HOSTS. No configuration values are supplied here. Prerequisites: Python; MySQL. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: MySQL credentials; optional SSH key/tunnel.

Can it modify data or perform write operations?

Documented write actions include: INSERT; UPDATE; DELETE. Recorded permission boundary: Configured MySQL grants.

What data-handling boundary should I consider?

Database data/results are returned to the client. Recorded sensitive-access context: Database contents; Credentials; SSH connectivity.

What limitations and risks should I check before use?

The server can read and mutate MySQL data; use a least-privilege account and restrict remote transport exposure. Single statements only. INSERT, UPDATE and DELETE are supported and destructive. Remote exposure needs host and origin controls. No independent runtime, installation, or comprehensive security audit was performed.

Is this an official MCP?

designcomputer is listed as Community implementation in MCP100’s current evidence.