Skip to main content
Glama
ByteTora

mysql-mcp-server-all

by ByteTora

Related Servers

Alternatives to mysql-mcp-server-all

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Production-grade MySQL MCP server with multi-source YAML config, read-only default, supporting metadata inspection, querying, and optional modules via stdio or HTTP.
      -
    • F
      license
      A
      quality
      C
      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
      -
    • 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.
      262 npm
      18
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A secure, read-only MySQL database proxy using MCP protocol, enabling SQL queries and table inspections via HTTP.
      10 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Read-only MySQL MCP server that lets AI agents list tables, describe schemas, and run SELECT/SHOW/EXPLAIN queries with a row cap, bound to a single database for safety.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A MySQL MCP server for local stdio clients, enabling database queries and management with read-only/write modes, audit logging, and configurable security.
      1,352 npm
      MIT

    TDQS

    A3.8/5.0

    Scored across 3 tools

    Disambiguation4/5

    The tools are largely distinct: execute_sql runs arbitrary read-only queries, get_schema_info returns column metadata, and get_table_sample fetches sample rows. However, execute_sql can also perform SELECT queries that return sample data, creating some overlap with get_table_sample.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: execute_sql, get_schema_info, get_table_sample. This makes the toolset predictable and easy to navigate.

    Tool Count4/5

    Three tools is a reasonable count for a focused read-only MySQL exploration server. While on the smaller side, each tool serves a clear purpose and the set does not feel overly thin.

    Completeness4/5

    The domain is well-covered for read-only database exploration: arbitrary SQL queries, schema metadata, and sample rows cover the core needs. Missing functionality like listing all tables can be achieved via execute_sql, so there are no major gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues