godot-interactive
Installation
SKILL.md
Godot Interactive
Use a persistent godot-mcp session to work on Godot 4.x projects without rediscovering the editor state every turn. This skill is the Godot analogue of playwright-interactive: it keeps one live editor connection alive when possible, combines it with file-based scene/script/shader tools, and requires explicit validation evidence before signoff.
Prefer the smallest evidence-producing loop. For live-editor tasks, stay on the live godot_editor_* and godot_runtime_* surface unless a file-only detail is truly required.
Preconditions
godot-mcpmust be configured for the current project.- For live editing, Godot 4.x must be running with the target project open and the AI Bridge plugin enabled.
- The bridge target should come from the active
godot_mcpMCP configuration.127.0.0.1:6550is a common default, but local setups may override it. - For automated gameplay input or screenshots, prefer the first-class
godot_runtime_*tools when they are present. If they are absent, fall back to a project-provided runtime harness or manual verification. - If tool choice is unclear, call
godot_helpfirst. - If the bridge is unavailable, continue with file-based tools and manual Godot review instead of inventing live-editor results.
- Treat a dropped bridge connection as a session problem. Reconnect before doing more live-editor work.
- If the user explicitly targets the running editor or currently open scene, treat the connected editor project as the source of truth. Do not burn time reconciling it with the shell workspace unless the task also depends on workspace files or the user suggests the wrong editor is open.