Runtime debugging and live project inspection via godot-mcp. Use when headless tools cannot diagnose the problem: code compiles but runtime behavior is wrong, tests pass but the game does not work as expected, or you need to inspect live state (node tree, console output, rendering). Escalation trigger: a task has failed 2+ times through the headless path (headless-build, gdunit-driver), or the iss
Receba novas skills de Desenvolvimento toda segunda
1 email curto, só com as skills novas de Desenvolvimento. 4 minutos de leitura, sem spam, cancela com 1 clique.
Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.
Ler descrição completaRecolher descrição
MCP Driver — Runtime Debug & Inspection
$ARGUMENTS
When to use this skill
MCP is the upgrade path when faster tools hit a wall. The fast loop handles most issues:
| Problem type | Fast path (no MCP) | |---|---| | Syntax / parse error | headless-build | | Unit test failure | gdunit-driver | | API lookup | godot-api |
Escalate to MCP when:
Compile-pass / runtime-fail — headless-build says OK but something is wrong when the game actually runs
Test-pass / behavior-wrong —
[Description truncada. Veja o README completo no GitHub.]