mysql-mcp-pro
Related Servers
Alternatives to mysql-mcp-pro
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProduction-ready MCP server for MySQL databases enabling AI assistants to interact with MySQL through secure, validated, and audited tools.2MIT
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server for MySQL database integration with AI agents, enabling database exploration, CRUD operations, schema management, and performance monitoring through natural language.744 npmMIT
- FlicenseNot gradedqualityDmaintenanceA high-performance MCP server that enables AI assistants to safely interact with MySQL databases through secure CRUD operations, schema inspection, and parameterized queries with built-in SQL injection prevention.1-
- AlicenseNot gradedqualityDmaintenanceA MySQL MCP server for secure database interaction, enabling schema inspection, query execution, and RBAC via AI coding assistants.1,352 npm5MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that connects AI agents to MySQL databases for schema exploration, data querying, and SQL execution via natural language.2MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive Model Context Protocol server that enables AI assistants to interact with MySQL databases through secure, role-based database operations.4MIT
TDQS
Scored across 21 tools
Each tool has a clear, distinct purpose. Ping and get_server_status differ; listing tools for databases, tables, views, routines, triggers are all separate. Query tools (execute_query, execute_select, get_table_data, count_rows, explain_query, export_query) each serve different needs. Process and transaction management tools are unambiguous.
All tool names use lowercase snake_case with a consistent verb_noun pattern (list_databases, describe_table, execute_query, begin_transaction, etc.). The only slight deviation is 'er_graph' which is a noun, but it still fits the descriptive style. Overall, naming is predictable and uniform.
21 tools cover a comprehensive range of database operations (connection, inspection, querying, export, process management, transactions). While on the higher side, each tool serves a specific purpose and the count is reasonable for a full-featured MySQL MCP server; slight reduction could be possible but not necessary.
The tool set covers most essential database operations: connection check, status, schema listing, query execution (with safety variants), analysis, export, process management, and transactions. Missing dedicated tools for schema DDL (create/alter/drop) and user management, but these can be accomplished via execute_query. Minor gaps but overall solid.