Skip to main content
Glama
shibbirweb

mcp-mysql-read-only

by shibbirweb

Related Servers

Alternatives to mcp-mysql-read-only

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to securely interact with MySQL databases, including listing tables, viewing schemas, and executing read-only SQL queries through natural language.
      6
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to directly query MySQL databases, list tables, and view table structures through natural language.
      10 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to safely query MySQL databases with read-only access, featuring SQL injection protection, connection pooling, and automatic query limits for secure database exploration.
      4
      115 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to interact with MySQL databases through read-only queries, with optional write capabilities in a controlled, auto-rolled-back manner.
      10 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to execute secure SQL queries against a MySQL database through the Model Context Protocol, with read-only operations by default and optional write/DDL capabilities.
      525 npm
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables an AI assistant to query and browse multiple database engines read-only, with the ability to switch connections and engines dynamically during a session.
      18
      91 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes: connection management (connect, use_connection, list_connections, current_connection), database selection (list_databases, use_database), schema inspection (list_tables, describe_table, get_table_indexes, get_foreign_keys), and data sampling (get_table_sample, run_query). However, there is slight overlap between get_table_sample and run_query (both can retrieve data), and between list_connections and current_connection, though descriptions clarify the difference.

    Naming Consistency4/5

    The naming is mostly consistent with verb_noun (e.g., list_tables, describe_table, use_database, get_table_indexes). The only minor deviation is the use of 'current_connection' as a noun phrase instead of a verb, and 'run_query' is fine. The pattern is predictable and readable.

    Tool Count4/5

    12 tools is a reasonable number for a database inspection server. Each tool serves a clear purpose, and the count is within the typical 3-15 range, though it's on the higher end. No tool feels extraneous, and the set covers connection management and schema exploration comprehensively.

    Completeness3/5

    The server covers connection management and schema inspection well, but it lacks write operations (by design, since it's read-only) and query execution is limited to read-only. Missing tools like 'list_views' or 'get_table_data' (full table dump) would be nice, but the core read-only workflow is covered. The read-only limitation is intentional, so the surface is fairly complete for its stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues