MCP bridge lets AI agents drive the Godot editor
It exposes Godot's editor internals as ~39 MCP tools so Claude, Codex, and friends can build scenes without touching a mouse.

What it does
The project is a Godot editor plugin paired with a Python server that speaks the Model Context Protocol. Together they translate natural-language requests from supported AI clients into live edits inside the Godot editor—creating nodes, wiring signals, tweaking materials, and running scenes. It is distributed through the Godot Asset Library and runs a local WebSocket bridge so the editor and the Python MCP server stay in sync.
The interesting bit
The real depth is in the Windows troubleshooting section: the maintainers diagnosed a nasty uv hard-link race condition where shared .pyd files lock the cache, and they ship both an automatic cache purge and a UV_LINK_MODE=copy env pin to neuter it. That level of systems-level debugging in a game-dev plugin is unexpected.
Key highlights
- Exposes over 120 operations across roughly 39 MCP tools covering scenes, UI, animations, particles, and cameras.
- Auto-configures 19+ MCP clients—Claude Code, Codex, Cursor, Zed, and others—through a dock panel inside Godot.
- Ships with anonymous, opt-out telemetry that hashes project-directory names before they leave the machine.
- Includes working demos, such as a cyberpunk HUD and a voxel block-world game, built entirely via AI prompts.
- Runs entirely local: the HTTP server binds to
127.0.0.1:8000and talks to the editor over a WebSocket on port 9500.
Caveats
- The Python server still requires
uvto be present on the host, so it is not a pure one-click Godot plugin install. - Windows users may hit stale
.pydlock issues unless the plugin’s cache mitigations or manual cleanup steps are applied. - Asset Library releases lag behind GitHub, so the one-click install from Godot’s built-in store may not be the latest version.
Verdict
Worth a look if you want LLMs to manipulate Godot scenes as first-class citizens rather than just generating code in a side panel. Skip it if you prefer keeping your editor fully manual or if running a local Python server alongside Godot feels like too many moving parts.
Frequently asked
- What is hi-godot/godot-ai?
- It exposes Godot's editor internals as ~39 MCP tools so Claude, Codex, and friends can build scenes without touching a mouse.
- Is godot-ai open source?
- Yes — hi-godot/godot-ai is open source, released under the MIT license.
- What language is godot-ai written in?
- hi-godot/godot-ai is primarily written in GDScript.
- How popular is godot-ai?
- hi-godot/godot-ai has 1.2k stars on GitHub and is currently cooling off.
- Where can I find godot-ai?
- hi-godot/godot-ai is on GitHub at https://github.com/hi-godot/godot-ai.