Godot AI MCP
An MCP server for the Godot engine: connects Claude Code, Claude Desktop and Codex to a live editor to build scenes, scripts and materials
- 3,509 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Modifies scene, script and resource files of the open Godot project
- The local server listens on machine ports, though restricted to loopback access
Install
- Works in
Manual install
Download a release from GitHub Releases and place the addon at your-project/addons/godot_ai/. In Godot, enable the plugin: Project → Project Settings → Plugins → Godot AI. In the Godot AI dock, press Configure for your client (Claude Code, Claude Desktop, Codex and others) — the configuration command is generated automatically.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Modifies scene, script and resource files of the open Godot project
- The local server listens on machine ports, though restricted to loopback access
This is third-party code. Review the repository files before installing.
What it does
Godot AI connects an MCP client to an open Godot editor through an editor plugin and a local Python server. The agent gets dozens of tools to build scenes, edit nodes and GDScript, wire up signals, UI, materials, animation, particles, cameras and environments, and search for scene and resource files in the project. The connection runs through two local hops with rotating access tokens: from the MCP client to the Python server, and from there to the editor over WebSocket, both restricted to the local machine. C# support is limited to writing files and finding symbols, without building or reporting compiler errors.
Who it is for. For Godot game developers who want to build scenes and logic through an agent directly inside the open editor.
Good fit when
- You want the agent to create and edit nodes, scenes and GDScript in an open Godot project
- You need to configure UI, materials, animation, particles or environments through a conversation with the agent
- You need to quickly find scenes or resources of a specific type in a large project
- You need to write and run tests for Godot scenes
Not a fit when
- Your Godot project is below version 4.7
- You need full C# builds with compiler error output — the server does not provide this
- Godot is closed or the editor is not running: the server only works with an open editor
Example request
Create a Camera3D named MainCamera in the current scene and wire its signal to the existing player scriptMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
GODOT_AI_DISABLE_TELEMETRY- Set to true to fully disable anonymous usage telemetry.
Limitations
Requires Godot 4.7 or later in the 4.x line, uv installed to run the Python server, and at least one MCP client. C# support is partial: writing and symbol search only, no builds. Access control does not protect against a compromised process running as the same user, and on Windows it also does not isolate other local accounts.
How to disable. Disable the plugin in Godot: Project → Project Settings → Plugins → Godot AI, and remove the server entries from your MCP client's configuration.
FAQ
Do I need a model account or cloud subscription?
No, the server does not choose a model provider, it only connects an MCP client to the Godot editor.
Does the server collect data about my project?
Telemetry records an installation UUID, event, platform and version, not code, scene contents, or project and file names; the project directory path is hashed. Disable it with GODOT_AI_DISABLE_TELEMETRY.
Discussion
No questions or reviews yet.
Related
MCP serversA .NET addon lets an agent drive the Godot editor: scenes, nodes, scripts, viewport screenshots and queries in the RQL language
An MCP server for the Godot engine: launch the editor, run projects and edit scenes from an agent
MCP for the Godot editor: an agent edits scenes, runs the game, freezes time and verifies its own work by playtest
An addon makes the Godot 4.2 and newer editor an MCP server with over 150 operations and a tool set that grows on request.
An MCP server for Godot 4 that runs inside the editor: the agent edits scenes, nodes and scripts, runs the project and reads the debugger, no Node.js
An MCP server and plugin for Godot 4.4+: the agent edits scenes and scripts in the editor, runs the game and reads errors
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Godot AI (this card) | yes | API key | 3,509 | |
| Roblox Studio MCP (community, debugging and playtests) | no | not required | 366 | MCP server for Roblox Studio |
| Godot MCP Full Control | no | not required | 513 | an MCP server with 157 tools for Godot 4 |
| Godot MCP Native | no | not required | 874 | an MCP server for Godot 4 that runs inside the editor |
README in short
The README describes Godot AI as a production-grade MCP server for Godot with 46 tools and over 120 operations for scenes, nodes, scripts, signals, UI, materials, animation, particles, cameras and environments. The architecture has three local hops: an MCP client, a Python server on authenticated HTTP, and the editor plugin over authenticated WebSocket, both ports loopback-only. Supported clients include Claude Code, Claude Desktop, Codex, Antigravity, Hermes Agent, DeepSeek Harness, Cursor, VS Code and Oh My Pi. MIT licensed.