MCP Server for MySQL
Related Servers
Alternatives to MCP Server for MySQL
No user-submitted related servers found.
Related Servers
- AlicenseBqualityNot gradedmaintenanceEnables secure interaction with MySQL databases through listing tables, reading data, and executing SQL queries with proper error handling and controlled access.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables interaction with MySQL databases through connection management, SQL execution, and schema exploration. It features multi-connection support and a safety-focused 'dangerous mode' for write operations.7 npm4MIT
- FlicenseAqualityCmaintenanceEnables agents to interact with MySQL databases securely, supporting multi-database read-only queries, protected DML writes, and streaming exports to Sandbox Datasets.5-
- AlicenseNot gradedqualityBmaintenanceProvides MySQL access with configurable per-connection capabilities, enabling secure read-only or writable database operations through Claude Code and other MCP clients.MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables direct interaction with MySQL databases through SQL queries, table exploration, and schema inspection with support for prepared statements and connection pooling.-
- FlicenseNot gradedqualityCmaintenanceEnables secure SQL query execution on MySQL databases with authentication and permission control, allowing users to explore database tables and run read-only queries.-
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clearly defined purpose for running read-only SELECT queries.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'mysql_query' follows a clear and descriptive pattern.
A single tool is too few for a MySQL server, as it severely limits functionality. The scope suggests a database server, but with only read-only queries, it lacks essential operations like INSERT, UPDATE, DELETE, or schema management.
The tool surface is severely incomplete for a MySQL server. It only supports read-only SELECT queries, missing all other CRUD operations, data manipulation, schema changes, and administrative tasks, which will cause significant agent failures.