Godot Interactive (MCP)

Drive a running Godot game from an agent: launch it, look at it, click it, inspect the scene tree, read and write node properties, call methods, and run dev-console commands — an observe → interact → observe loop that replaces manual playtesting for anything verifiable.

The two halves

1. godot-mcp — a Node MCP server. Spawns/kills the Godot process, captures its stdout, and wraps a file protocol into game_* tools.
2. GodotMCPBridge — a GDScript autoload running inside the game. Polls a command file every frame, executes commands on the live tree, writes responses and screenshots.

Everything interactive goes through the bridge. If the bridge isn't loaded or isn't being found, every game_* tool times out while run_project still reports success.

Limitation: the MCP spawns its own Godot process. It cannot attach to a game you launched with F5 from the editor.