Skip to main content
Glama
ramakrishnanayyappan

mysql-diag-mcp

by ramakrishnanayyappan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mysql-diag-mcp

No user-submitted related servers found.

    Related Servers

    • mysql-mcp-server

      mukul975
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server for MySQL database operations, providing secure HTTP endpoints for read-only queries, performance analysis, and server monitoring.
      133 npm
      18
      MIT

    • mysql-mcp

      zuozhu20100425
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables secure, read-only access to MySQL databases with structured query tools, and optional opt-in write operations when explicitly enabled.
      600 npm
      MIT

    • mysql-mcp

      rlembo06
      A
      license
      Not graded
      quality
      D
      maintenance
      A lightweight MCP server providing safe, read-only access to MySQL databases. It enables users to query multiple MySQL instances securely while preventing write operations.
      630 npm
      MIT

    • mysql-mcp

      qxduddes
      F
      license
      A
      quality
      A
      maintenance
      Security-hardened, read-only MySQL MCP server that enables safe, read-only access to MySQL databases for running SELECT queries, exploring schemas, and sampling data via MCP clients.
      9
      -

    • mysql-mcp

      charlesaugust44
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MySQL MCP server that provides a safe_query tool for executing SELECT and SHOW queries while blocking write operations, designed for use with OpenCode.
      600 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target clearly distinct diagnostic areas: connectivity, processlist, status, variables, InnoDB internals, replication, and explain. The only notable overlap is among mysql_processlist, mysql_active_queries, and mysql_monitor_clients, all of which read the processlist but with different filtering/grouping purposes.

    Naming Consistency4/5

    All tools share the mysql_ prefix and use snake_case with descriptive resource names, making the set predictable. A minor deviation is that mysql_ping and mysql_explain use action-style names while the rest are noun-phrase resources, but this does not create real confusion.

    Tool Count4/5

    16 tools is slightly above the typical 3-15 range, but the count is justified by the breadth of MySQL diagnostic concerns: processlist, status, InnoDB transactions, locks, wait events, table IO, and replication. Each tool covers a distinct diagnostic probe rather than duplicating existing functionality.

    Completeness4/5

    The toolkit provides strong coverage for diagnosing MySQL health, performance, locks, transactions, and replication with no obvious dead ends. Minor gaps exist, such as no ability to kill a query or inspect slow query logs, but these are operational actions rather than core diagnostic surface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources