godot-interactive

Maintains a persistent godot-mcp session to inspect and edit Godot 4.x scenes, nodes, and tests.

Updated Apr 18, 2026

Search Tags:#csharp #godot #godot-mcp #live-editor #scene-inspection #runtime-diagnostics

Ready to run

npx skills add https://github.com/Zearain/ludum-dare-59 --skill godot-interactive

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: godot-interactive
Source: https://github.com/Zearain/ludum-dare-59/tree/main/.opencode/skills/godot-interactive
Command: npx skills add https://github.com/Zearain/ludum-dare-59 --skill godot-interactive

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Persistent Godot workflows and AI Bridge integration enable continuous editor state, reducing reloads and reconfiguration when working on Godot 4.x C# projects.

Core Features & Use Cases

Persistent godot-mcp session keeps the editor connection alive for iterative scene edits, inspection, and diagnostics.
File-based and live-editor workflows integrate scene/Script/Shader changes with runtime validation, run/stop loops, and hybrid file-plus-editor checks.
Use cases include scene inspection, iterative node edits, runtime diagnostics, and validation across .tscn, .cs, .gdshader, and .tres.

Quick Start

Start a persistent godot-mcp session and begin iterative scene edits for your Godot 4.x C# project.

Frequently Asked Questions about godot-interactive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I edit Godot 4.x scenes without reloading the editor state?▼

Live Godot editing with persistent editor state keeps the godot-mcp session alive, allowing iterative scene edits, node inspections, and runtime diagnostics without reloading. It coordinates file-based changes and live-editor checks across .tscn and .tres files.

What is the best way to run runtime diagnostics on Godot C# scripts during development?▼

Runtime diagnostics for Godot C# scripts are handled by running build cycles and capturing explicit validation results like dotnet build outputs and runtime logs. This QA-driven workflow requires minimal evidence and explicit sign-off before finalizing any claims.

Can I use live editor workflows to inspect nodes and update .gdshader shaders in Godot?▼

Yes, live editor workflows support inspecting nodes and updating .gdshader shaders in Godot. The persistent session integrates scene, script, and shader changes with runtime validation and run/stop loops for hybrid file-plus-editor checks.

Does Godot MCP support validating changes through build and run cycles?▼

Godot MCP validates changes through explicit build and run cycles, requiring dotnet build outputs and scene state evidence before finalizing claims. This enforces a QA-driven workflow with an inventory and explicit sign-off for all edits.

Why does my Godot editor require reconfiguration when working on C# projects iteratively?▼

Persistent Godot workflows solve the problem of continuous editor state loss, reducing reloads and reconfiguration when working on Godot 4.x C# projects. The session maintains a live connection for iterative development.

When do I need a persistent godot-mcp session for Godot scene inspection?▼

A persistent godot-mcp session is needed for iterative scene edits, node inspections, and runtime diagnostics across .tscn, .cs, and .tres files in Godot 4.x projects. It coordinates live edits and file-based changes seamlessly.