mcp-mysql-explorer
Related Servers
Alternatives to mcp-mysql-explorer
No user-submitted related servers found.
Related Servers
- 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.MIT
- AlicenseNot gradedqualityDmaintenanceA robust MCP server for interacting with MySQL databases through AI agents, providing tools for schema analysis, query execution, and dynamic connection management with read-only security.MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server for MySQL databases that enables schema exploration, query execution, and resource access through a unified interface. It features a LangGraph-based agent that translates natural language into SQL queries with automatic error recovery and schema discovery.-
- FlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to safely explore and interact with MySQL databases through dynamic tool generation from stored procedures. It provides database discovery capabilities and intelligent procedure categorization while enforcing security restrictions to prevent data modification.-
- AlicenseNot gradedqualityDmaintenanceA MySQL MCP server for secure database interaction, enabling schema inspection, query execution, and RBAC via AI coding assistants.7MIT
- FlicenseNot gradedqualityBmaintenanceAn MCP server that exposes relational databases (PostgreSQL/MySQL) to AI agents with natural language to SQL query support.19-
TDQS
Scored across 7 tools
The read/write split between query and execute_sql is explicitly stated in both descriptions, so an agent can pick correctly. The introspection tools (describe_table, get_table_indexes, get_create_table) overlap somewhat since DESCRIBE/SHOW can also surface keys and index info, but each has a distinct output focus.
All names are snake_case, but verb conventions are mixed: list_tables/describe_table use one verb family, while get_table_indexes/get_create_table/get_database_info use 'get', and query/execute_sql are bare verb forms. Readable overall, but 'get_create_table' is awkward and the pattern isn't uniform.
Seven tools is well-scoped for a MySQL explorer: schema discovery, ad-hoc read queries, writes, and database metadata each have exactly one owner. No tool feels redundant padding.
The surface covers introspection, read queries, write DDL/DML, and database-level info, so core workflows are supported. Minor gaps exist around database/schema switching (e.g. listing databases or selecting a schema) and explicit transaction control, which agents would have to work around with raw SQL.