godot-interactive

Godot Interactive Workflow

Use this skill for repeatable Godot project interaction: inspect the current files, make a bounded change, run the game, send input, collect state and diagnostics, and leave an evidence-backed result.

Current MCP surface

This repository exposes one catalog tool and eighteen grouped tools. The grouped tools are:

core_manage, project_manage, scene_manage, filesystem_manage, validation_manage, runtime_manage, node_manage, input_manage, signal_manage, animation_manage, camera_manage, physics_manage, render_2d_manage, render_3d_manage, audio_manage, ui_manage, network_manage, and system_manage.

Start with:

{ "domain": "runtime" }

passed to godot_catalog. The response lists the exact operation names and schemas for that domain. Then call the matching grouped tool:

{
  "op": "game_wait",
  "params": { "frames": 5, "frameType": "render" }
}

The outer object is passed to runtime_manage. Never promote an operation name into a standalone MCP tool name, and always include params as an object.

Transport and lifecycle

There is no editor-side AI Bridge in this repository and no editor connection API on TCP port 6550. The server launches the Godot project, copies/injects its interaction autoload, and connects to the runtime interaction server at 127.0.0.1:9090. Runtime commands only work after a project is running and the injected server has initialized.

Start a project with:

{
  "op": "run_project",
  "params": {
    "projectPath": "C:/games/demo",
    "scene": "res://scenes/main.tscn"
  }
}

passed to core_manage. The scene parameter is optional. Stop it with { "op": "stop_project", "params": {} }. Use { "op": "get_debug_output", "params": {} } on core_manage for captured stdout/stderr. There is no separate connect, disconnect, editor refresh, or editor-save phase in this public tool tree.

Session loop

1. Establish a baseline

Inspect project metadata and persisted scene structure before changing anything: