godot-live-edit

Godot Live Project Editing

Use this skill for a tight inspect → edit → validate → run → verify loop in a Godot 4 project. It targets the MCP surface implemented by this repository, not an editor plugin API.

Transport boundary

This repository does not provide a live editor AI Bridge. TCP port 6550 is not a transport used by this server, and there is no editor connection step to perform. The server launches Godot itself, injects its runtime interaction autoload into the project, and connects to that runtime interaction server on 127.0.0.1:9090.

All calls use the public grouped MCP tools:

godot_catalog
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
system_manage

Call godot_catalog first, optionally with {"domain":"scene"}, then call the selected manager with the required envelope:

{
  "op": "<operation from the catalog>",
  "params": { }
}

op is an operation value, not an MCP tool name. params is required even when the operation takes no arguments. The catalog returned by this repository is the source of truth when an operation schema is unclear.

Inspect before editing

Use absolute projectPath values for project-backed operations. Scene and file paths are relative to the project unless the operation description says otherwise.

{
  "tool": "core_manage",
  "arguments": {
    "op": "get_project_info",
    "params": { "projectPath": "C:/games/demo" }
  }
}

Read a scene without starting Godot:

{
  "tool": "scene_manage",
  "arguments": {
    "op": "read_scene",
    "params": {
      "projectPath": "C:/games/demo",
      "scenePath": "res://scenes/main.tscn"
    }
  }
}

For project settings or files, use project_manage with read_project_settings or list_project_files, and filesystem_manage with read_file. Do not assume a node path: reacquire the scene tree or scene JSON after structural edits.