Godot AI is an MCP server and editor plugin that connects AI assistants to a live Godot editor. Its 46 tools and more than 120 operations let an agent build scenes, edit nodes and scripts, wire signals, and configure UI, materials, animation, particles, cameras, and environments, as well as search the project and run its test suite.
The plugin starts the server from inside Godot and shows connection status in a dock, where a Configure button writes the client entry for each detected MCP client. Supported clients include Claude Code, Claude Desktop, Codex, Antigravity, Hermes Agent, DeepSeek Harness, Cursor, VS Code, and Oh My Pi. GDScript is fully supported: scripts written through the tools are parse-validated, hot-reloaded, attached, and outlined. C# support is text-only, so the tools write and outline C# files but do not build them.
A request travels from the MCP client through a stdio bridge to a local Python server and then over a WebSocket to the editor plugin. Both local hops authenticate with independent rotating capabilities and never fall back to unauthenticated access, and the editor connection stays loopback-only. An agent in a container or on another machine reaches the editor by running the bridge over SSH. Usage telemetry records events, outcomes, and versions but not code, scene contents, or file names, and it can be turned off.
Features
- Editor tools: 46 tools and 120+ operations for scenes, nodes, scripts, signals, UI, materials, animation, particles, cameras, and environments
- GDScript support: scripts written by the agent are parse-validated, hot-reloaded, attached, and outlined
- C# files: writes, patches, and outlines C# scripts, without building .NET or reporting compiler errors
- One-click client setup: a dock button configures each detected MCP client at user, project, or local scope
- Supported clients: Claude Code, Claude Desktop, Codex, Antigravity, Hermes Agent, DeepSeek Harness, Cursor, VS Code, and Oh My Pi
- Authenticated bridge: both local hops use rotating capabilities, and the editor connection stays loopback-only
- Remote agents: agents in containers or on other machines connect by running the bridge over SSH
- Game testing: runs the project's scene test suite from the agent
- In-editor updates: a dock Update button upgrades the add-on and repins client entries
- Opt-out telemetry: records usage events without code, scene contents, or file names
