Skip to main content
Glama
gistrec

mcp-mysql-client

by gistrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-mysql-client

No user-submitted related servers found.

    Related Servers

    • MySQL MCP Server

      lm203688
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to safely interact with MySQL/MariaDB databases, supporting read-only queries by default with optional write operations and access control.
      MIT

    • mysql-mcp

      mcp-research
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to query and manage MySQL databases through a structured MCP interface, supporting SQL execution, table inspection, and database operations.
      9
      13 npm
      MIT

    • readonly-db-mcp

      mir-shakir
      A
      license
      A
      quality
      C
      maintenance
      Safe MySQL database exploration for AI agents via MCP, enabling read-only queries and schema inspection with three-layer write protection.
      9
      MIT

    • MCP MySQL Server

      efeabio
      A
      license
      Not graded
      quality
      D
      maintenance
      A 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 npm
      MIT

    • DatabaseMCP

      LeoVegaSys
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables AI agents to safely explore and interact with MySQL databases through dynamic tool generation from stored procedures. It provides database discovery capabilities and intelligent procedure categorization while enforcing security restrictions to prevent data modification.
      -
    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

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: server_info covers connection state, list_tables and describe_table cover schema discovery, query executes read-only SQL, explain returns execution plans, and execute handles mutations. The only mild overlap is between query and explain, but their outputs and use cases are sufficiently different that an agent should not select the wrong one.

    Naming Consistency3/5

    The tool names are all lowercase and readable, but they do not follow one consistent pattern: list_tables and describe_table use verb_noun, explain and execute are bare verbs, while server_info and query are noun-style names. This is a mixed convention rather than a chaotic one, but it still falls short of a uniform naming scheme.

    Tool Count5/5

    Six tools is a well-scoped set for a MySQL client server. Each tool covers a distinct part of the interaction surface: server diagnostics, table enumeration, schema inspection, read queries, query planning, and write execution, so none feel redundant or missing.

    Completeness5/5

    The tool set covers the full expected workflow for a MySQL client: understand the environment, discover tables, inspect schema, run read queries, analyze plans, and perform DML writes. DDL and transactions are explicitly excluded by design, so their absence is not an unexpected gap within the server's declared scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources