Skip to main content
Glama
wenb1n-dev

mysql_mcp_server

by wenb1n-dev

Related Servers

Alternatives to mysql_mcp_server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Multi-database management tool and MCP server supporting MySQL, PostgreSQL, SQLite, and Dameng DM8, enabling AI assistants to query and manage databases via stdio or HTTP.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables natural-language Chinese queries across MySQL, Dameng DM, and KingbaseES databases, with safe SQL generation, schema exploration, and read-only query execution.
      -
    • A
      license
      B
      quality
      D
      maintenance
      Provides comprehensive MySQL database operations including CRUD, performance optimization, health analysis, and anomaly detection. Supports multiple connection modes, OAuth2.0 authentication, and role-based permissions for database management through natural language.
      9
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A universal SQLite database management tool that enables SQL query execution through MCP protocol. Supports SELECT/INSERT/UPDATE/DELETE/CREATE operations with built-in SQL injection protection across stdio, SSE, and streamable-http communication modes.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to interact with a 达梦 DM8 database over stdio, providing read-only queries, schema exploration, and optional gated write/DDL operations with strict safety checks.
      9
      10 npm
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables SQL queries, schema exploration, and Oracle sequence management across multiple databases including Oracle, OceanBase, and DolphinDB. Supports multiple environments with secure password handling.
      -

    TDQS

    B3.1/5.0

    Scored across 5 tools

    Disambiguation3/5

    The tools have distinct primary purposes (SQL execution, field name conversion, table structure/index/name retrieval), but there is some overlap between get_table_desc, get_table_index, and get_table_name as they all involve table metadata retrieval, which could cause confusion about which to use for specific queries. Descriptions help clarify, but the boundaries are not perfectly clear.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case (e.g., execute_sql, get_table_desc), with no deviations in style or convention. This predictability makes it easy for agents to understand and navigate the tool set.

    Tool Count4/5

    With 5 tools, the count is reasonable and well-scoped for a MySQL server, covering core operations like SQL execution and table metadata access. It is slightly lean but not insufficient, as it avoids bloat while providing essential functionality.

    Completeness2/5

    The tool set is severely incomplete for a MySQL database server. It lacks basic CRUD operations (e.g., create_table, update_data, delete_table), data manipulation beyond raw SQL, and lifecycle management tools, leaving significant gaps that will hinder agent workflows and cause failures in typical database interactions.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive