mysql-mcp-server
Provides an MCP server that offers read-only exploration and querying of MySQL databases: listing databases, listing tables, describing table schemas, and executing read-only SQL (SELECT/SHOW/DESCRIBE/EXPLAIN) with safeguards like timeouts, row limits, and query validation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Security claims are mostly at the application/query level (read-only allowlisting, query validation, timeouts, row limits). TLS enforcement, exact query validation robustness, and secret logging hygiene are not explicitly evidenced in the provided content. Best practice is to use a least-privilege MySQL user restricted to SELECT/metadata and to ensure the MySQL client uses TLS as configured.
⚡ Reliability
Best When
You want agent-driven read-only database browsing and sampling using an MCP-capable client, with a dedicated MySQL user that has only least-privilege SELECT/metadata access.
Avoid When
You cannot guarantee least-privilege MySQL credentials or you need strict assurances beyond basic query allowlisting/timeouts/limits.
Use Cases
- • Allowing LLM/agent users to explore MySQL schemas (databases/tables/columns)
- • Running safe, read-only analytical queries with guardrails
- • Automating DBA/analyst workflows like schema inspection and sampling rows
Not For
- • Executing data-modifying statements (INSERT/UPDATE/DELETE/DDL)
- • Performing large, high-cardinality queries without considering row limits/timeouts
- • Handling highly sensitive environments without careful database user permissions
Interface
Authentication
Authentication is delegated to MySQL credentials configured via env vars. No OAuth/scoped auth layer is described at the MCP layer.
Pricing
No pricing information provided in the supplied content.
Agent Metadata
Known Gotchas
- ⚠ Agents may attempt disallowed SQL; responses/errors may depend on the internal query validation implementation.
- ⚠ Row limits/timeouts may truncate results; agents should be prepared to refine queries.
- ⚠ Schema/table names may require correct database selection (default database may be used if database argument omitted).
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-03-30.