mysql-mcp
Related Servers
Alternatives to mysql-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables MCP clients to dynamically connect to MySQL, MariaDB, and PostgreSQL databases via connection URLs, and to administer databases, tables, and records.-
- FlicenseNot gradedqualityDmaintenanceProvides MySQL database integration for AI assistants and other MCP clients, allowing them to list tables, read table data, and execute SQL queries.-
- AlicenseNot gradedqualityCmaintenanceEnables executing SQL queries against a MySQL database via MCP, returning results as JSON.1,282,895 npmMIT
- FlicenseNot gradedqualityCmaintenanceProvides a read-only interface to local MySQL databases via MCP, enabling listing databases, tables, describing schemas, and querying rows with structured filters.-
- -licenseNot gradedqualityCmaintenanceEnables interaction with a MySQL database through MCP tools, resources, and prompts, supporting both read-only queries and safe write operations.-
- FlicenseAqualityBmaintenanceMCP server that lets clients run SQL (select/insert/update/delete) against a MySQL database, with readonly and readwrite modes.4-
TDQS
Scored across 11 tools
Several tools have unclear boundaries: execute_sql and execute_query appear to do nearly the same thing, and fetch_table may overlap with execute_query for reading data. An agent could easily select the wrong generic tool despite the clear CRUD/schema tools.
Most names follow a predictable verb_noun snake_case pattern (list_tables, count_rows, delete_rows). Minor inconsistencies exist, such as insert_row singular vs update_rows/delete_rows pluralched and execute_sql vs execute_query using different nouns for the same conceptual operation.
11 tools is a reasonable size for a database MCP server case. However, execute_sql and execute_query are redundant, so not every tool clearly earns its place.
The set covers health, database/table listing, schema inspection, row CRUD, counting, and arbitrary SQL, so core database operations are well covered. Dedicated table lifecycle operations are missing but can be handled through execute_sql, making this a minor gap rather than a fatal one.