godot-mcp
Related Servers
Alternatives to godot-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceEnables AI assistants to interact with and manipulate Godot game engine projects, including creating projects, launching editor, managing scenes and nodes.121ISC
- AlicenseBqualityCmaintenanceEnables AI clients to inspect Godot 4 project settings, create GDScript and .tscn scene files, and optionally communicate with the Godot editor to open or run scenes and capture 2D or 3D viewport screenshots.101MIT
- AlicenseBqualityDmaintenanceEnables AI-assisted Godot 4.x game development within a secure sandbox, covering project management, file operations, asset discovery, GDScript generation, and optional runtime execution.4051 PyPI2MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to interact with the Godot game engine, including launching the editor, running projects, capturing debug output, and managing scenes.8470 PyPI1MIT
- AlicenseBqualityCmaintenanceEnables AI agents to inspect, modify, run, and debug Godot projects, including scene and script analysis, editor and project management, and visual verification through screenshots.2219 npm14MIT
- AlicenseAqualityDmaintenanceEnables AI agents to create, edit, and run Godot 4.5+ games by providing tools for project scaffolding, scene manipulation, and engine interaction. It supports full game development workflows including node editing, script attachment, and project execution with debugging capabilities.245MIT
TDQS
Scored across 6 tools
Each tool targets a distinct object (project, scene, node, script) or a distinct action (set main scene, validate), so misselection is unlikely. The only mild overlap is between create_project (which auto-creates a main scene) and set_main_scene, but the descriptions make the boundary clear.
All six tools follow a consistent snake_case verb_noun pattern (create_project, create_scene, add_node, create_script, set_main_scene, validate_project). No mixed conventions or vague verbs.
Six tools is a well-scoped set for Godot project scaffolding: each tool covers a distinct lifecycle step (project, scene, node, script, main scene, validation). Nothing feels redundant or missing at the count level.
Creation is well covered, but the surface is write-only: there is no way to read/list existing scenes or scripts, remove nodes/scenes/scripts, or edit an existing script's content. An agent cannot inspect project state, which will cause dead ends in any non-trivial workflow.