Godot MCP Toolkit
Related Servers
Alternatives to Godot MCP Toolkit
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables 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.46MIT
- 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 agents to read and edit Godot 4.x scenes and resources, introspect the class API, run the game in a managed headless process with frame stepping, input injection and screenshots, validate scripts, and diagnose code via a built-in GDScript LSP plus a bridge to an already open editor.23MIT
- AlicenseAqualityCmaintenanceConnects AI assistants to the live Godot 4 editor so they can build scenes, scripts, resources and animations, run the game, simulate input, capture screenshots and playtest scenarios, and diagnose runtime errors. Every edit flows through undoable changesets that can be diffed, approved, checkpointed or discarded.291MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to automate the Godot Engine editor, including scene authoring, node transforms, tilemap editing, animation, shaders, and live GDScript execution via MCP.10022MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI-driven control of Godot 4 for scene manipulation, 3D import, procedural textures, deterministic playtesting, game generation, and publishing to itch.io and Steam.6MIT
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.