Skip to main content
Glama
3281831403

cubrid-mcp-server

by 3281831403
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to cubrid-mcp-server

No user-submitted related servers found.

    Related Servers

    • MCP MySQL Server

      yuru-sha
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to interact with MySQL databases by inspecting schemas and executing safe, read-only queries within transactions.
      6 npm
      10
      MIT

    • MySQL MCP Server

      lm203688
      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

    • MCP MySQL Server

      Iceeeeec
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to safely query MySQL databases with read-only access by default, supporting table listing, structure inspection, and SQL queries with optional write operation control.
      16 npm
      MIT

    • mcp-db-server

      rudraraval4
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLM clients to query SQL databases via natural language with read-only, AST-validated, and capped queries, ensuring safety guarantees.
      2
      MIT

    • mcp-server-mysql

      fcmyoo
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to inspect MySQL database schemas and execute read-only queries via the Model Context Protocol.
      12,398 npm
      MIT

    • easy-mysql-mcp

      chenkumi
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to inspect and query a MySQL database through safe, structured tools, including schema discovery and read-only queries.
      9
      130 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 11 tools

    Disambiguation4/5

    Each tool has a distinct primary purpose, but schema_definitions and describe_table overlap on column metadata, and describe_table also overlaps with list_indexes on index information. Agents could initially confuse schema_definitions with describe_table, though the descriptions clarify the difference.

    Naming Consistency3/5

    Names are readable and mostly snake_case, but conventions are mixed: verb-led names (filter_table_names, describe_table, list_indexes, execute_query) coexist with noun-led names (all_table_names, schema_definitions, table_row_counts, health_check). A uniform verb_noun pattern would improve predictability.

    Tool Count5/5

    Eleven tools is well within the ideal range for a database introspection server. Each tool addresses a distinct need—discovery, schema, indexes, query planning, execution, and health—without feeling bloated or sparse.

    Completeness4/5

    The surface covers table discovery, schema/index metadata, row counts, serials, class hierarchy, query execution, and plan tracing—strong coverage for read-only CUBRID introspection. Minor gaps like foreign-key metadata or object-level DDL are absent but can be worked around via execute_query.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources