Skip to main content
Glama
eeantoss

mysql-mcp-server

by eeantoss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mysql-mcp-server

No user-submitted related servers found.

    Related Servers

    • mysql-mcp-server

      myheisenberg
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables MySQL database operations through MCP, including executing SQL queries, listing databases and tables, and describing table structures.
      959 npm
      5
      MIT

    • mysql-mcp-demo

      Khushboo-Mishra
      -
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with a MySQL database through MCP tools, resources, and prompts, supporting both read-only queries and safe write operations.
      -

    • MySQL MCP Server

      qq5032449
      A
      license
      A
      quality
      A
      maintenance
      Enables secure interaction with MySQL databases through MCP, offering tools for SQL queries, schema inspection, and data sampling, with support for multiple databases, SSH tunnels, and safe write operations.
      3
      1
      MIT

    • MySQL MCP Server

      2506013878
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MySQL database management via MCP, allowing users to list databases, tables, views, and functions, inspect table schemas, create tables, and modify table fields.
      Apache 2.0

    • MariaDB-MCP

      TheNesdark
      F
      license
      A
      quality
      C
      maintenance
      Enables interaction with MariaDB/MySQL databases via MCP, supporting read-only mode, SQL execution, and schema inspection.
      6
      -
    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

    C2.9/5.0

    Scored across 14 tools

    Disambiguation2/5

    Several tools have overlapping purposes: database_execute_sql, database_execute_script, and database_execute_batch all execute SQL but with subtle differences, while database_connect, database_connect_environment, and database_switch_environment cover similar connection territory. The presence of check_node_version, which has nothing to do with database operations, further confuses tool selection.

    Naming Consistency3/5

    Most tools follow a consistent database_verb_noun pattern (e.g., database_connect, database_execute_sql), but the lone check_node_version breaks the convention entirely. The naming is readable but not fully uniform.

    Tool Count3/5

    At 14 tools, the count is at the high end of the typical range but still acceptable for a database server. However, the inclusion of check_node_version, which is unrelated to MySQL/PostgreSQL work, suggests the count could be reduced or the tool placed in a separate utility server.

    Completeness4/5

    The tool set covers core database operations well: connecting, disconnecting, testing, executing SQL (single, script, batch), retrieving schema, managing project environments, and listing sessions. Minor gaps like explicit transaction control are not critical for a basic MCP database server, so the surface is fairly complete.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources