fgui-agent-bridge
Related Servers
Alternatives to fgui-agent-bridge
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables AI coding agents to directly operate FairyGUI Editor for UI assembly, animation creation, asset import, and package publishing through structured MCP and CLI commands.471MIT
- 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
- AlicenseNot gradedqualityDmaintenanceMCP 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
- FlicenseNot gradedqualityDmaintenanceA 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.1-

Funplay MCP for Unityofficial
AlicenseNot gradedqualityAmaintenanceThis 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.304MIT- AlicenseNot gradedqualityCmaintenanceAn 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.1MIT
TDQS
Scored across 76 tools
The tool set has clear domain groupings, but several near-neighbor tools create real misselection risk: insert_object vs insert_text/insert_loader/insert_list, add_keyframes vs add_transition_item vs set_keyframe vs update_transition_item, and delete_package_item vs remove_object vs remove_transition vs remove_movieclip. The descriptions often explain the boundaries, but an agent must read carefully to avoid choosing the wrong operation.
Every tool uses the fgui_ prefix and snake_case, with predictable verb_noun forms such as fgui_create_component, fgui_get_tree, fgui_set_property, and fgui_verify_document. The few diagnostic names like fgui_ping and fgui_status are minor exceptions within an otherwise highly consistent convention.
With 76 tools, the surface is far beyond the typical 3-15 range and is heavily fragmented into specialized variants for resources, transitions, verification, branches, and object creation. Even for a feature-rich FairyGUI editor bridge, this volume creates excessive selection and maintenance overhead for an agent.
The surface is very broad: project selection, branches, packages/items, documents, object trees, properties, transitions, movie clips, lists/groups, publishing, references, and verification are all represented. There are some notable gaps, such as package-level create/delete and branch deletion, but most core workflows have coverage.