MCP Server for MySQL — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow driver and database-version changes affecting connection and query tools

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

Best fit

LLM-assisted MySQL schema inspection and controlled query/write workflows.

What we know

A MySQL MCP server with schema inspection, SQL queries, optional writes, SSH tunnels, multi-database support and PII redaction.

Maintenance / activity evidence

Observed Jul 27, 2026 (UTC)Merge pull request 143 from chrstphe/mcp-toplist-badge

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.
Privileges of configured MySQL account. Writes: INSERT; UPDATE; DELETE when enabled.
MySQL credentials; remote bearer/TLS as configured.
Sensitive access: Database contents, Credentials, Potential PII

Direct database access can expose or modify sensitive records; use least-privilege accounts and keep write flags disabled unless needed.

Security source · repository notice ↗

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

Popularity

2,143 repository stars · 44.1k package downloads / 30 days

Stars observed Oct 6, 2026. Downloads observed Oct 6, 2026.

All limitations / Review context

What MySQL versions and operation safeguards does the current server support?

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.

Direct database access can expose or modify sensitive records; use least-privilege accounts and keep write flags disabled unless needed.
Privileges of configured MySQL account.
MySQL credentials; remote bearer/TLS as configured.
Database records and query results are exposed to the MCP client.
Reviewed write actions: INSERT; UPDATE; DELETE when enabled
Sensitive access: Database contents, Credentials, Potential PII
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
Write operations are opt-in but can mutate production data.
Remote mode adds endpoint/auth/TLS configuration.

Original activity observations

2026-07-27T13:36:52Z: Merge pull request 143 from chrstphe/mcp-toplist-badge

Technical identity

github.com/benborla/mcp-server-mysql

Exact implementation source: https://github.com/benborla/mcp-server-mysql ↗
Reviewed resource type: MCP Server
Repository identity: benborla/mcp-server-mysql
Package identity: npm:@benborla29/mcp-server-mysql

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 ↗
benborla/mcp-server-mysql
Recorded repository material and project history.
Package registry ↗
@benborla29/mcp-server-mysql
Recorded package identity, distribution or download evidence.
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

Publisher sample uses root; MCP100 should explicitly advise least-privilege DB user.
Publisher-specific exact credential-revocation procedure not established; use the issuing provider controls only if credentials actually exist.
Credential revocation is external-provider-specific or not documented in examined official project Setup/README; do not assert exact revocation CLI.
Publisher example uses MYSQL_USER=root; never use the sample against a production database. Prefer restricted credentials. The client JSON above substitutes safe placeholders. Requires intentional review of consent, secrets, local paths, or third-party deployment before execution.
publisher README config shape, placeholders adapted for safety Replace the supplied credential/path placeholders privately; use only the named configuration schema.
Run the removal command in the same client and configuration scope used for registration; this does not uninstall an application, revoke third-party authorization, or delete data.

Install / connect
Publisher instructions
Current publisher README uses `claude mcp add mcp_server_mysql -e MYSQL_HOST=... -e MYSQL_PORT=... -e MYSQL_USER=... -e MYSQL_PASS=... -e MYSQL_DB=... -- npx @benborla29/mcp-server-mysql`. Require least-privilege database user and avoid README root account example in production.
Advanced configuration · client registration
client registration · Review before use
claude mcp add mcp_server_mysql -e MYSQL_HOST="127.0.0.1" -e MYSQL_PORT="3306" -e MYSQL_USER="root" -e MYSQL_PASS="your_password" -e MYSQL_DB="your_database" -- npx @benborla29/mcp-server-mysql
Configure / authenticate
MCP100 setup guide
Set MYSQL_HOST, MYSQL_PORT, MYSQL_USER, MYSQL_PASS, MYSQL_DB using a dedicated minimal read-only MySQL account; do not use the README root password example. Keep ALLOW_INSERT_OPERATION, ALLOW_UPDATE_OPERATION, ALLOW_DELETE_OPERATION and ALLOW_DDL_OPERATION false for default safe setup.
Advanced configuration · claude desktop json
{ "mcpServers": { "mcp_server_mysql": { "args": [ "-y", "@benborla29/mcp-server-mysql" ], "command": "npx", "env": { "MYSQL_DB": "your_database", "MYSQL_HOST": "127.0.0.1", "MYSQL_PASS": "<DB_PASSWORD>", "MYSQL_PORT": "3306", "MYSQL_USER": "<LIMITED_DATABASE_USER>" } } } }
Check connection
Suggested check
Confirm the client discovers mysql_query and mysql://tables, then list schema/tables or run a simple read-only SELECT using sandbox credentials. Never enable write env flags as part of connection testing. Client registration check: `claude mcp get mcp_server_mysql` (checks registration; inspect tools/read-only calls separately to verify authenticated service access).
Remove / uninstall / revoke
MCP100 setup guide
Remove the matching MCP configuration from the client. This does not uninstall the local package or revoke provider credentials. Client disconnect (claude-code, only if registered using the name `mcp_server_mysql`): `claude mcp remove mcp_server_mysql`. This unregisters the client entry; it does not uninstall packages or revoke remote service credentials.
claude mcp remove mcp_server_mysql

Official Documentation & Sources

What it does

A MySQL MCP server with schema inspection, SQL queries, optional writes, SSH tunnels, multi-database support and PII redaction.

Capability: Data & Databases
Resource type: MCP Server
Best fit: LLM-assisted MySQL schema inspection and controlled query/write workflows.

Representative uses

Inspect schemas
Run SQL queries
Query multiple databases
Enable controlled insert/update/delete operations

Limitations

Write operations are opt-in but can mutate production data.
Remote mode adds endpoint/auth/TLS configuration.

Reviewed access

Access & risk

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

Authentication: MySQL credentials; remote bearer/TLS as configured.
Permissions: Privileges of configured MySQL account.
Data handling: Database records and query results are exposed to the MCP client.
Cost: free
Risk and cautions: Direct database access can expose or modify sensitive records; use least-privilege accounts and keep write flags disabled unless needed.

Access scope and cautions

Write actions: INSERT UPDATE DELETE when enabled
Sensitive access: Database contents Credentials Potential PII
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: Inspect schemas; Run SQL queries; Query multiple databases; Enable controlled insert/update/delete operations.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx @benborla29/mcp-server-mysql. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: MYSQL_HOST; MYSQL_PORT; MYSQL_USER; MYSQL_PASS; MYSQL_DB; ALLOW_INSERT_OPERATION; ALLOW_UPDATE_OPERATION; ALLOW_DELETE_OPERATION. No configuration values are supplied here. Prerequisites: Node.js 20+; MySQL 5.7+. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Database credentials; bearer auth/TLS available for remote mode.

Can it modify data or perform write operations?

Documented write actions include: INSERT; UPDATE; DELETE when enabled. Recorded permission boundary: Privileges of configured MySQL account.

What data-handling boundary should I consider?

Database records and query results are exposed to the MCP client. Recorded sensitive-access context: Database contents; Credentials; Potential PII.

What limitations and risks should I check before use?

Direct database access can expose or modify sensitive records; use least-privilege accounts and keep write flags disabled unless needed. Write operations are opt-in but can mutate production data. Remote mode adds endpoint/auth/TLS configuration. A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.

Is this an official MCP?

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