A Node.js MCP server combines Godot scene-file operations with editor and project launch tools. For Codex, 1 route is explicitly documented by the integration maintainer.
A Node.js MCP server combines Godot scene-file operations with editor and project launch tools.
Platforms: See documentation
MCP transport compatibility is inferred; this agent is not explicitly documented for this connection.
Node.js 18+ and an installed Godot executable configured for the server.
Some tools edit scene files or launch a project rather than controlling an already open editor session.
Godot’s command line supports project execution, scripts and headless exports.
Platforms: Windows, macOS, Linux
The native interface is documented, but no setup for this coding agent is established by this source.
An installed Godot executable; export operations also need the appropriate export templates and presets.
Headless execution and export do not provide interactive control of an already open editor.
A Godot project server combining file-based scene edits with an optional live editor bridge.
Platforms: Windows, macOS
MCP support suggests compatibility; this client is not documented by the maintainer.
A built MCP server; Godot and the companion editor plugin are needed for live editor operations.
File operations edit scene files directly; live-editor operations require a plugin in an open Godot editor.
A native MCP server with live Godot editor and headless fallback modes.
Platforms: Windows, macOS, Linux
MCP support suggests compatibility; this client is not documented by the maintainer.
Godot 4.5 or newer and the server binary matching the Godot version.
Live editing requires an enabled editor plugin; without it, the server uses file and headless workflows.
A GDScript editor addon that serves MCP tools from the running Godot editor.
Platforms: Not documented
The integration documentation explicitly names this client.
Godot with the project addon enabled; a compatible MCP client and proxy if required.
The in-editor server uses SSE transport, so some clients need a transport proxy.
| Integration | Codex compatibility | Requirements |
|---|---|---|
| Godot MCP | MCP compatibility (inferred) Setup guide | Node.js 18+ and an installed Godot executable configured for the server. |
| Godot command line | Not documented | An installed Godot executable; export operations also need the appropriate export templates and presets. |
| Godot MCP · YasiruRF | MCP compatibility (inferred) | A built MCP server; Godot and the companion editor plugin are needed for live editor operations. |
| Godot MCP · zeegzoog | MCP compatibility (inferred) | Godot 4.5 or newer and the server binary matching the Godot version. |
| Godot MCP · lifeiscontent | Documented setup Setup guide | Godot with the project addon enabled; a compatible MCP client and proxy if required. |
The sources establish the capabilities listed above, not complete application coverage. Check each bridge’s limitations and your application version before starting.
Choose a route that explicitly documents Codex and matches your environment. Start with the maintainer’s setup guide and a disposable project copy. Shared MCP support alone is listed as an inference.
All Godot Engine integrations