mcp-driver

What problem does it solve?

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.

Core Features & Use Cases

• Runtime debug-fix loop: Runs the project, captures console output (including errors/warnings), analyzes the root cause, applies a targeted fix, and verifies the result across up to three iterations.
• Live inspection for hard cases: Escalates when headless builds pass but gameplay is wrong, tests pass but behavior is incorrect, visuals are broken, input doesn’t respond, physics misbehaves at runtime, or you need to inspect live node state and logs.
• Correct tool routing: Provides clear escalation triggers and explicitly avoids misuse for compile/syntax errors, unit test failures, or API lookups.

Quick Start

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.