Live editing & the running game

This is what sets Godot MCP Studio apart: your AI doesn't just edit files on

disk, it can work with the live editor and even the game while it's playing.

Live editor tools

With Godot open and the addon enabled, live tools connect to the editor over a

local, token-secured WebSocket. Your AI can read the real scene tree, inspect

node properties as they actually are, and make edits to the currently open scene

that show up instantly in the editor. Edits go through Godot's own undo system,

so Ctrl+Z works exactly as you'd expect.

The running game

When you play your scene, Godot MCP Studio injects a small runtime service into

the game. Through it, your AI can, while the game runs:

• Read the live scene tree and node properties.
• Change properties and call methods on live nodes.
• Simulate input: key presses, actions, mouse.
• Capture in-game screenshots.
• Read performance (FPS, frame time) and control time scale or pause.

This makes "play the game, see what's wrong, fix it" an actual loop the AI can

run.

How the handoff is secured

Each play session gets its own short-lived token. The editor addon acts as a

multiplexer: it relays game_* requests to the running game and relays results

back, and it drops relays that go stale. Nothing listens on a public port;

everything is loopback only, and every message is authenticated.

Requirements

Live tools need the editor open with the addon enabled, and for running-game

tools, the game actually playing. If they return a "not connected" style error,

check both. See Troubleshooting.