Godot MCP Toolkit
Related Servers
Alternatives to Godot MCP Toolkit
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to directly control a running Godot editor for autonomous game development, including scene building, tilemap and animation manipulation, UI automation, and live GDScript execution.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to build, run, and debug Godot projects by editing scenes and scripts, inspecting live game state, injecting input, capturing viewports, and examining native debugger state through 42 tools.European Union Public 1.2
- AlicenseAqualityAmaintenanceEnables AI assistants to automate the Godot Engine editor, including scene authoring, node transforms, tilemap editing, animation, shaders, and live GDScript execution via MCP.479MIT
- AlicenseCqualityBmaintenanceEnables AI assistants to interact with the Godot Engine editor and projects, including scene editing, script management, physics queries, and asset operations.1261MIT
- AlicenseCqualityAmaintenanceEnables AI agents to interact with the Godot game engine, including project inspection, scene/script parsing, headless exports, runtime control with live scene-tree inspection and evaluation, and API documentation search.100462 npm2MIT
- AlicenseNot gradedqualityDmaintenanceProvides a comprehensive integration between LLMs and the Godot Engine, enabling AI assistants to intelligently manipulate project files, scripts, and the live editor. It supports advanced workflows including version-aware documentation querying, automated E2E game testing, and real-time visual context capture.10 npm26MIT
TDQS
Scored across 43 tools
Most tools have distinct purposes, but get_server_info and get_capabilities overlap heavily in scope. Additionally, add_node vs load_sprite vs create_ui_node create ambiguity around which node-creation tool to use, though descriptions partially clarify.
All tool names follow a consistent verb_noun snake_case pattern, such as list_scenes, create_project, and inspect_node. There are no deviations or mixed conventions, making the naming highly predictable.
With 43 tools, the server is substantially over the recommended 3-15 range. While the domain is broad, the sheer number creates a heavy cognitive load and suggests insufficient consolidation of related operations.
The toolkit covers core Godot workflows like scene editing, scripting, running, and testing, but lacks basic delete operations for files, scenes, and projects. This leaves notable gaps in lifecycle management, especially since create and duplicate operations exist without corresponding removals.