fgui-agent-bridge
Related Servers
Alternatives to fgui-agent-bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP 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
- AlicenseNot 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.17MIT

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.240MIT- AlicenseNot gradedqualityAmaintenanceAn 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
- FlicenseAqualityAmaintenanceMCP 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-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to control the Unity Editor externally, providing tools for scene, GameObject, component, and other editor operations.1MIT
TDQS
Scored across 24 tools
Each tool targets a distinct operation: create/insert/remove, undo/redo, save/discard, publish, project selection, and property manipulation. Even similar tools like status and ping are differentiated by whether they wake the editor.
All tool names follow a consistent snake_case pattern with the fgui_ prefix, and the action verb typically comes first (insert_object, remove_object, save_document, get_project). No mixed conventions or unpredictable naming.
With 24 tools, the server is at the upper end of the 16-25 range, which feels heavy. However, each tool serves a distinct purpose in the FairyGUI editing workflow, so the count is borderline but not excessive.
The tool set covers core editing operations like object manipulation, property setting, undo/redo, and publishing, but lacks a delete_component operation and a direct get_property tool. This means some lifecycle operations are missing, leaving notable gaps.