Skip to main content
Glama
Wilson520403

fgui-agent-bridge

by Wilson520403

Related Servers

Alternatives to fgui-agent-bridge

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      B
      maintenance
      Enables AI coding agents to directly operate FairyGUI Editor for UI assembly, animation creation, asset import, and package publishing through structured MCP and CLI commands.
      47
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI agents to control and interact with Godot 4 editor, allowing scene manipulation, file editing, and project inspection through natural language.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server for Cocos Creator 3.8+ that enables AI assistants to interact with the editor via 50+ tools for scene, node, component, prefab, asset, and project management.
      27 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server integrates AI assistants with Unity Editor, allowing them to create scenes, generate scripts, simulate input, and automate workflows using 91 built-in tools.
      265
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that translates human GUI actions into machine-executable commands, enabling AI agents to control real software applications like Zoom, Excel, and WeChat via natural language or API calls.
      1
      MIT
    • F
      license
      A
      quality
      A
      maintenance
      MCP server that connects AI coding assistants to a live Godot editor, enabling scene, node, script, resource, runtime, debugger, and test workflows through natural language.
      45
      -

    TDQS

    B3.2/5.0

    Scored across 48 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions, but fgui_set_property overlaps with specialized setters such as fgui_set_text_style, fgui_set_list_layout, fgui_set_group_layout, fgui_set_relation, and fgui_set_gear_display, and its whitelist is not enumerated. fgui_status and fgui_ping also have related bridge-health purposes, though their descriptions differentiate them. Overall mostly distinct with a few boundary ambiguities.

    Naming Consistency4/5

    The fgui_ prefix is applied uniformly, and most names follow a verb_noun pattern like fgui_get_tree, fgui_create_button, and fgui_remove_transition. A few exceptions (fgui_status, fgui_ping, fgui_undo, fgui_redo, fgui_publish) break the verb_noun pattern but remain readable and conventional.

    Tool Count2/5

    48 tools far exceeds the typical 3-15 range and feels heavy for a single MCP server. Although the FairyGUI domain is broad, many operations could be consolidated, such as import_image/import_font/import_sound, the transition item CRUD trio, and the specialized layout property setters.

    Completeness3/5

    Core editing workflows are well covered, including transitions, controllers, properties, asset import, publishing, and verification. However, notable lifecycle gaps remain: no package create/delete/rename, no generic removal for image/font/sound assets (only MovieClip has explicit removal), and no generic object creation beyond button, component, and insert-existing-resource operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues