MySQL Bridge
Related Servers
Alternatives to MySQL Bridge
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables read-only MySQL database access, allowing listing databases, tables, describing schemas, and executing SELECT/SHOW/DESCRIBE/EXPLAIN queries.712 npm4MIT
- FlicenseNot gradedqualityDmaintenanceEnables safe interaction with MySQL databases through SELECT queries, table structure inspection, and database schema exploration. Provides read-only access to query data and examine database metadata.1-
- AlicenseNot gradedqualityDmaintenanceEnables schema introspection and safe read-only queries on MySQL databases, supporting table/column discovery, relationship exploration, and controlled SELECT queries.7 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables read-only access to MySQL databases through natural language queries. Provides automatic table schema discovery and executes SELECT, SHOW, DESCRIBE, and EXPLAIN statements within secure read-only transactions.MIT
- AlicenseNot gradedqualityDmaintenanceProvides read-only access to MySQL databases, enabling schema inspection, table listing, and execution of SELECT queries through the Model Context Protocol.362 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides read-only access to MySQL databases, enabling schema exploration, table inspection, and safe SELECT query execution via MCP.1-
TDQS
Scored across 3 tools
Each tool serves a clearly distinct purpose: listing tables, describing a table's schema, and executing arbitrary read-only queries. There is no overlap or ambiguity, so an agent can easily select the right tool for the task.
Two tools follow the verb_noun pattern (list_tables, describe_table), while 'query' is a bare verb. This is a minor deviation, but the naming remains predictable and readable, and the overall style is consistent (snake_case).
Three tools is a small but reasonable footprint for a read-only database bridge. They cover the core operations (listing, describing, and querying) without unnecessary bloat, though a slightly larger set could be justified.
For a read-only MySQL bridge, the surface covers the essential workflows: discovering available tables, understanding schema, and running arbitrary queries. A potential gap is lack of transaction or metadata utilities, but these are not expected for a simple bridge.