← Index

MySQL MCP

io.github.gistrec/mcp-mysql-clientv1.0.0Databases

MCP server for one MySQL database: schema, read-only queries and guarded writes.

The current version, v1.0.0, was published to the official MCP registry on 2026-08-23. It is distributed as mcp-mysql-client on npm, filed under Databases by this index, and declares 12 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using MySQL MCP in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-08-23).

Contracts can change after screening, with no version bump. The gate pins MySQL MCP’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Environment variables
MYSQL_HOST

Database host.

MYSQL_PORT

Database port.

MYSQL_USER
required

MySQL user. Use one with the least privileges the task needs, never root.

MYSQL_PASS
secret

Password for that user. Treat it as a secret; MYSQL_PASS_FILE reads it from a file instead.

MYSQL_DB
required

The one database this server is bound to. No tool can leave it.

MYSQL_SSL

Require a TLS connection to the server.

MYSQL_SSL_CA

Path to the CA bundle verifying the server certificate; implies MYSQL_SSL.

ALLOW_INSERT_OPERATION

Allow INSERT statements through the execute tool.

ALLOW_UPDATE_OPERATION

Allow UPDATE statements through the execute tool.

ALLOW_DELETE_OPERATION

Allow DELETE statements through the execute tool.

MYSQL_MAX_ROWS

Row cap for one read; the result is marked truncated when it is hit.

MYSQL_TIMEOUT_MS

Statement timeout in milliseconds; the connection is dropped on expiry.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
20
installability
25
documentation
15
stability
10
Alternatives in Databases