mysql-mcp-server-by-cdata
Provides a local MCP (Model Context Protocol) server that exposes MySQL data via tools for listing tables/columns and running SQL SELECT queries (read-only MCP). It wraps CData JDBC Driver for MySQL and is intended for use with MCP-capable desktop clients (e.g., Claude Desktop) over stdio.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Security is largely delegated to the CData JDBC Driver configuration (credentials in the JDBC URL/connection properties via the .prp). The README does not describe TLS requirements, secret redaction/logging, query allowlisting, or any authentication at the MCP tool layer. Because a SQL SELECT execution tool is exposed, agents should be constrained to safe/limited queries to reduce data exfiltration risk.
⚡ Reliability
Best When
You want to query a local MySQL instance (or reachable MySQL) from an MCP-enabled desktop client with minimal setup and only read access.
Avoid When
You need remote/networked MCP access, strict query safety/whitelisting, or robust operational controls like rate limits, retries, and structured error contracts.
Use Cases
- • Let an LLM query live MySQL data without writing SQL (e.g., answering questions about operational metrics).
- • Data exploration: list available tables and columns and then retrieve subsets via SELECT queries.
- • Integrate local MySQL read access into an MCP-enabled desktop workflow.
Not For
- • Production deployment as a network-accessible API service (stdio-only, local use).
- • Full CRUD operations via MCP tools (the README describes this as read-only).
- • Handling sensitive data in untrusted environments without controls (the tool can run arbitrary SELECT SQL).
Interface
Authentication
The MCP server itself is launched locally with a .prp file that references the JDBC driver and JDBC URL. The README mentions that if the data source uses OAuth you may need to authenticate in a browser, but it does not describe OAuth flows or scopes at the MCP server layer.
Pricing
The README indicates licensing for the CData JDBC Driver. No explicit pricing tiers for the MCP server are provided.
Agent Metadata
Known Gotchas
- ⚠ Server uses stdio, so it must run on the same machine as the MCP client.
- ⚠ If a JDBC URL (or underlying CData driver) requires OAuth/browser auth, the setup may require interactive authentication steps before the server can function.
- ⚠ The run_query tool accepts raw SQL SELECT; an agent may generate inefficient or overly broad queries if not constrained.
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-by-cdata.
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.