Skip to main content
Glama
w48930429

FairyGUI Agent Bridge

by w48930429
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to FairyGUI Agent Bridge

No user-submitted related servers found.

    Related Servers

    • fgui-agent-bridge

      Wilson520403
      A
      license
      A
      quality
      B
      maintenance
      MCP server that enables AI agents to operate FairyGUI Editor through structured tools, using a local JSON file queue and the editor plugin to invoke FairyGUI APIs.
      24
      54
      MIT

    • cocos-mcp-server

      caravanglory
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI assistants to directly control the Cocos Creator 3.8.x editor via MCP protocol, providing over 130 tools for scene, node, component, asset, and project operations.
      27 npm
      41
      MIT

    • Talk to Figma MCP

      kctw-dev
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to directly control Figma Desktop via MCP, supporting UI creation, editing, prototyping, and variable management with over 60 tools.
      65
      1,138 npm
      1
      MIT

    • Xiangsu MCP

      sleepyquq
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to operate Douyin Xiangsu AR effects through MCP, including scene editing, asset binding, TypeScript scripting, compilation, preview screenshots, and interactive playtesting.
      10
      -

    • Cocos MCP Server

      andsky
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to directly control the Cocos Creator game editor via MCP protocol, supporting scene management, node manipulation, component attachment, and asset management.
      27 npm
      2
      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

    C2.9/5.0

    Scored across 47 tools

    Disambiguation2/5

    fgui_list_items and fgui_list_resources are nearly identical, and fgui_get_package_info also returns resource lists, creating clear ambiguity. Additionally, fgui_create_button overlaps with fgui_create_component. While most tools have distinct targets, these duplicates make misselection likely.

    Naming Consistency4/5

    The overwhelming majority of tools follow the fgui_verb_noun snake_case pattern (e.g., fgui_create_component, fgui_get_tree, fgui_remove_transition). Minor exceptions like fgui_status, fgui_ping, and fgui_undo/redo are acceptable but keep it from being perfectly uniform.

    Tool Count2/5

    With 47 tools, the server far exceeds the 25+ threshold for a heavy toolset. While the FairyGUI editor is complex, many functions are overly granular (e.g., 7 transition-related tools) and several could be merged, making the count feel excessive rather than well-scoped.

    Completeness3/5

    The toolkit covers a wide range of workflows including components, text styles, transitions, movieclips, imports, and publishing. However, obvious gaps exist such as no component deletion or renaming, no package creation, and no controller editing, which limits full lifecycle coverage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources