FairyGUI Agent Bridge
Related Servers
Alternatives to FairyGUI Agent Bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to drive a running FairyGUI Editor through structured MCP tool calls, so they can assemble UI components, import images/fonts/sounds, author Transition and MovieClip animations, preview layout snapshots, manage undo/save history, and publish resource packages. It bridges agents and the editor via a local JSON queue handled by a globally installed editor plugin, with an optional Skill to improve operation accuracy.1MIT
- AlicenseBqualityBmaintenanceMCP 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.7679MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to directly control the Cocos Creator 3.8+ editor, including scene and node manipulation, UI building, script attachment, validation, preview runtime logs, and screenshots.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables 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.44-
- AlicenseBqualityDmaintenanceEnables AI agents to directly control Figma Desktop via MCP, supporting UI creation, editing, prototyping, and variable management with over 60 tools.651MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to operate Douyin Xiangsu AR effects through MCP, including scene editing, asset binding, TypeScript scripting, compilation, preview screenshots, and interactive playtesting.28MIT
TDQS
Scored across 47 tools
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.
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.
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.
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.