Skip to main content
Glama
Esaban17

mcp-mysql-database

by Esaban17
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to mcp-mysql-database

No user-submitted related servers found.

    Related Servers

    • MySQL MCP Server

      kcsgh
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to query a live MySQL database using natural language through read-only tools for listing tables, describing schemas, and running SELECT queries.
      -

    • mysql-explorer

      awand795
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to interact with a MySQL database by automatically discovering its schema and retrieving full table data for analysis.
      -

    • MCP MySQL Server

      keleshteri
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Desktop to interact with MySQL databases through secure query execution, schema discovery, and multi-database support with configurable read/write permissions and built-in SQL injection protection.
      262 npm
      MIT

    • mysql-mcp-server

      Sharat005
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language querying of MySQL databases via Claude Code, allowing SELECT queries, table listing, and schema inspection.
      959 npm
      MIT

    • mcp-mysql

      TLazari
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude AI to execute MySQL queries, list tables, and describe table structures through natural language, with support for parameterized queries and connection pooling.
      262 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 19 tools

    Disambiguation4/5

    Each tool targets a distinct resource/action, and descriptions explicitly redirect overlaps (select_records points to run_query for joins; execute_sql notes it handles mass UPDATE/DELETE that update_records/delete_records also do). The execute_sql vs update_records/delete_records boundary and select_records vs run_query boundary are the only mild overlaps, but descriptions disambiguate well.

    Naming Consistency4/5

    Nearly all tools follow a consistent snake_case verb_noun pattern (list_connections, create_database, drop_table, insert_records, run_query, execute_sql). The single deviation is current_connection, a noun-only name, which is a minor inconsistency in an otherwise predictable scheme.

    Tool Count4/5

    19 tools is on the heavier side but each maps to a genuine operation across the connection, database, table, and record layers. The count is justified by the broad scope rather than redundant tooling, though it sits at the upper borderline.

    Completeness5/5

    Full lifecycle coverage: connections (list/current/select/add/remove), databases (list/create/use/drop), tables (list/describe/create/drop), records (full insert/select/update/delete CRUD), plus read-only run_query and write execute_sql for anything else. Schema alteration and advanced queries are handled via execute_sql/run_query, leaving no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources