mysql-readonly-mcp
Related Servers
Alternatives to mysql-readonly-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceRead-only MySQL MCP server that lets AI agents list tables, describe schemas, and run SELECT/SHOW/EXPLAIN queries with a row cap, bound to a single database for safety.3MIT
- AlicenseAqualityCmaintenanceA read-only MySQL MCP server supporting stdio, SSE, and Streamable HTTP transports, enabling secure querying and schema inspection of MySQL databases from MCP clients.3MIT
- AlicenseCqualityCmaintenanceConnects MCP-compatible clients like Claude to a MySQL database, enabling schema inspection and read/write queries via stdio transport.5317 npm1MIT
- FlicenseAqualityCmaintenanceRead-only MySQL database access via MCP. Enables listing databases, tables, schemas, running SELECT queries, and EXPLAIN plans.6-
- AlicenseNot gradedqualityCmaintenanceEnables safe querying and optional writing to MySQL databases via MCP tools, with support for schema inspection, connection management, and read-only mode.16 npm3MIT
- FlicenseNot gradedqualityDmaintenanceProvides read-only access to MySQL databases, enabling schema exploration, table inspection, and safe SELECT query execution via MCP.1-
TDQS
Scored across 6 tools
Each tool targets a clearly distinct introspection or query concern: server metadata, table listing, column/FK description, index listing, query execution, and plan explanation. The describe_table vs list_indexes boundary is clear (columns vs indexes), so an agent can reliably select the right tool.
All six tools use a consistent mysql_verb_noun snake_case pattern (get_server_info, list_tables, describe_table, list_indexes, query, explain). Predictable and uniform throughout.
Six tools is well-scoped for a read-only database server. Each tool earns its place across discovery (info, tables, describe, indexes) and querying (query, explain) with no redundancy.
The read-only surface covers introspection plus querying and plan analysis, which is solid for the stated purpose. Minor gaps like listing databases or schema-level search exist but are workable given the server targets a single configured database.