just-a-mysql-mcp
Related Servers
Alternatives to just-a-mysql-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceRead-only MCP server that lets AI agents safely query SQLite, PostgreSQL, and MySQL/MariaDB. Enforces read-only transactions with column masking, row caps, query timeouts, EXPLAIN-based cost rejection, and rate limiting.724 npm1MIT
- AlicenseAqualityBmaintenanceRead-only MCP server for querying PostgreSQL, MySQL, and SQLite from AI agents — multi-database, safe by default.417 npm1ISC
- AlicenseAqualityCmaintenanceRead-only MySQL/MariaDB MCP server for running SELECT queries safely, with automatic read-only enforcement and query limits.36 npmMIT
- FlicenseNot gradedqualityFmaintenanceA read-only MCP server that enables AI agents to explore database schemas and execute safe queries on PostgreSQL and MySQL.-
- 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
- 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.158 npmMIT
TDQS
Scored across 3 tools
The tools are mostly distinct in purpose: list_tables for table names, describe_table for column details, and mysql_query for arbitrary read-only SQL. However, mysql_query also supports DESCRIBE/DESC, creating a partial overlap with describe_table.
list_tables and describe_table follow a clear verb_noun pattern, but mysql_query deviates with a noun_verb structure. All names are snake_case and readable, so the inconsistency is minor.
Three tools is a minimal but well-scoped set for a read-only MySQL server. It is slightly on the small side, but each tool serves a distinct core need and the count fits the intentional minimalism.
The set covers the essential read-only workflow: discovering tables, inspecting schema, and running queries. Missing explicit tools for views/indexes are easily handled via mysql_query, so gaps are minor.