Skip to main content
Glama
mcp-mysql-client

mcp-mysql-client

Related Servers

Alternatives to mcp-mysql-client

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      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.
      8
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query and modify MySQL and MariaDB databases over MCP, with each connection independently permitting selects, inserts, updates, deletes, and DDL while defaulting to read-only and rejecting anything outside the allowed operations. Connections are configured in JSON, result sets are capped and truncated, and passwords stay server-side.
      MIT
    • 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
      11 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets AI agents read and propose writes to MariaDB and MySQL databases through MCP without holding database credentials, previewing exactly which rows each write would change, holding risky ones for human approval, and allowing any single change to be undone. Rules in YAML let safe writes through automatically while blocking or escalating the rest.
      1
      AGPL 3.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents and MCP clients to inspect MySQL databases and run read-only SQL queries through tools for listing databases, tables, schemas, and executing compact queries, with optional write mode and safety controls.
      4
      1
      MIT

    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 recent community issues