Godot Safe Change — Guarded MCP Workflow

Godot Safe Change gives MCP-capable AI agents a guarded workflow for changing Godot projects. It starts with the live editor context, previews bounded changes, requires explicit confirmation and revision/lease checks, applies through Godot's EditorPlugin or guarded file routes, verifies the resulting state, and only rolls back while the original history and revision still match.

Requirements

This skill provides agent instructions. It does not include the MCP server or Godot EditorPlugin. Install and connect godot-safe-change-mcp, enable the Godot Safe Change Bridge plugin in a Godot 4.x editor, and use an MCP-capable agent client. Node.js 22.22.2 or newer is required.

Setup and supported operations: https://github.com/LJH-snow/godot-safe-change-mcp#readme

What you get

• A preview, explicit confirmation, apply, and verification workflow.
• Guidance for supported scene, script, resource, input-action, and project-setting changes.
• Revision and lease checks that reject stale or conflicting changes.
• Guarded rollback that refuses to overwrite later user changes.

Boundaries

Only operations exposed by the connected server are supported. No arbitrary Godot RPC, arbitrary script execution, or unrestricted filesystem writes. Editor operations require a connected bridge. This is a free, MIT-licensed skill and project.