Run Godot debug builds and inspect live projects via godot-mcp.
npx skills add https://github.com/RandallLiuXin/GodotMaker --skill mcp-driver
Please help me install this Agent Skill. Skill: mcp-driver Source: https://github.com/RandallLiuXin/GodotMaker/tree/main/skills/core/mcp-driver Command: npx skills add https://github.com/RandallLiuXin/GodotMaker --skill mcp-driver
This Skill helps you diagnose problems that only show up when a Godot game is actually running, by enabling runtime debugging and live inspection through the godot-mcp workflow.
Use the mcp-driver skill to debug a runtime-only issue in a Godot project by launching it in debug mode, capturing the live output, applying fixes based on the error patterns, and re-running until the behavior matches expectations.
High-intent search queries and answers about installing and using this skill.
To debug Godot runtime errors where gameplay fails despite passing builds, you can use a runtime debug-fix loop. This launches a debug build, captures live console output, analyzes root causes, and applies targeted fixes across up to three iterations for verification.
Yes, you can inspect live Godot node state and logs to fix visual glitches and unresponsive input. By running a debug build through godot-mcp, you gain live project inspection capabilities to diagnose runtime physics misbehavior and missing node states.
The best way to capture console output for Godot physics misbehavior is running a debug build through an MCP server registered as "godot". This supports the run_project, get_debug_output, and stop_project loop to capture errors and warnings for root-cause analysis.
Yes, you need an MCP server specifically registered as "godot" to use this skill for gameplay validation. This registered server provides the necessary interface to execute run_project, get_debug_output, and stop_project commands for live inspection.
You should not use runtime debugging for Godot compile errors, syntax errors, unit test failures, or API lookups. This approach explicitly avoids misuse for static issues and is reserved for scenarios where headless builds pass but actual gameplay is incorrect.
Yes, the debug-fix loop supports up to three iterations for root-cause analysis in Godot projects. This allows you to run the project, capture debug output, apply a targeted fix, and re-run to verify that the behavior matches expectations.
alexmeckesManage persistent Godot 4.x editor sessions for scene inspection and live node edits.
adilkalamEnforce evidence-first debugging with logs, network, and state checks.
abdias98Reproduce test failures and runtime errors to isolate root causes.
SriRamkunamsettyAttach to Node.js processes via V8 inspector and CDP for debugging.
