mysql-mcp-server
Provides an MCP (Model Context Protocol) server for connecting to a MySQL database and exposing tools for SELECT-only querying, schema inspection (tables and columns), and execution-plan analysis via EXPLAIN/EXPLAIN ANALYZE. Also provides an execute tool for data-modifying statements (INSERT/UPDATE/DELETE) with a dry-run + confirmation token flow.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Security controls described include: SELECT-only restriction on the query tool, a two-step dry-run + confirmation token process for data modifications, and confirmation token expiry after 5 minutes. Access control appears to rely on database user permissions (no additional auth/authorization for MCP clients described). TLS enforcement is not explicitly documented; assume HTTPS/TLS may not apply because it is a local MCP subprocess—MySQL connection encryption is unspecified. Credential handling is described via environment variables, but logging/redaction behavior is not specified.
⚡ Reliability
Best When
You want an agent-friendly way to introspect and query a MySQL database locally/in your environment using MCP, and you can provide appropriately privileged (preferably read-only) credentials.
Avoid When
You need robust access control beyond database-user permissions, or you cannot enforce the two-step confirmation process for write operations.
Use Cases
- • Letting AI agents safely explore a MySQL schema (list tables, fetch table schema)
- • Answering questions over operational data using SELECT queries with result formatting
- • Performance troubleshooting by running EXPLAIN or EXPLAIN ANALYZE for a candidate query
- • Controlled, human/agent-mediated data changes (INSERT/UPDATE/DELETE) using a two-step dry-run + confirmation token workflow
Not For
- • Untrusted/anonymous clients or direct internet exposure
- • Environments that require strong user authentication/authorization at the API layer
- • Workloads requiring complex pagination controls or cursor-based retrieval
- • Bulk/long-running queries without governance (especially EXPLAIN ANALYZE)
Interface
Authentication
No separate end-user auth is described for the MCP server itself; access control is primarily via the MySQL user permissions configured in the environment.
Pricing
No pricing information provided; likely self-hosted.
Agent Metadata
Known Gotchas
- ⚠ The execute tool supports only INSERT/UPDATE/DELETE and uses dry_run + confirm_token; agents must follow the two-step pattern to avoid failed writes.
- ⚠ EXPLAIN ANALYZE may execute the query to gather real statistics; can be risky for long-running or heavy queries.
- ⚠ Query tool is restricted to SELECT statements only; agents may need to route data-modifying intent to the execute tool.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mysql-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.