Godot MCP

What Coding-Solo/godot-mcp MCP server does

Coding-Solo/godot-mcp MCP server exposes Godot project operations to AI agents through the Model Context Protocol. It can open the editor for a selected project, start a project in debug mode, stop execution, and return console output or error messages. It can also report the installed Godot version, search a directory for projects, and provide structural information about a project.

Scene-related operations cover creating a scene with a chosen root node type, inserting nodes with configurable properties, loading a sprite or texture into a Sprite2D node, saving scenes, and exporting a 3D scene as a MeshLibrary resource for GridMap use. For Godot 4.4 and newer, the server includes operations for reading file UIDs and refreshing UID references by resaving resources.

How it works

Coding-Solo/godot-mcp MCP server runs locally as a Node.js package and communicates with an MCP client over the client’s configured command transport. Basic requests, such as opening the editor or reading project information, invoke Godot’s built-in command-line functions directly. More involved scene operations are delegated to one bundled GDScript file, godot_operations.gd.

The operations script receives an operation name and parameters as JSON. This design lets the server pass different scene-management requests to Godot without creating a separate temporary script for every request. The target project must be a directory containing a project.godot file.

Setup and configuration

Install Godot Engine and Node.js 18 or later with npm before configuring Coding-Solo/godot-mcp MCP server. An MCP-capable AI client is also required. The package can be launched with npx -y @coding-solo/godot-mcp, or the repository can be built locally with npm install, followed by npm run build; a client can then point to build/index.js.

Godot is detected automatically when possible. Set GODOT_PATH when the executable is not found automatically or when a particular installation should be used. Set DEBUG to true to enable detailed server-side logging. After adding the server to a client, restart or refresh the client if its tools do not appear.

The documented client configurations include Cursor and Cline. Cursor requires the Agent chat profile to run MCP tools, and the README notes that Cursor Pro or Business may be required. Claude Code is also shown as a supported setup method, although it is not one of the client labels represented in this directory’s compatibility field.

Tools and capabilities

Coding-Solo/godot-mcp MCP server provides the following operation groups:

• Launch the Godot editor for a project.
• Run and stop a project programmatically.
• Read debug output and error messages.
• Retrieve the installed Godot version.
• Find projects under a specified directory.
• Inspect project details and structure.
• Create scenes and add nodes with selected properties.
• Load sprites or textures into Sprite2D nodes.
• Export 3D scenes as MeshLibrary resources.
• Save scenes, including variant-saving options.
• Read file UIDs and update project UID references on Godot 4.4+.

These capabilities are intended for local Godot workflows where the agent needs feedback from project execution or direct scene manipulation rather than only editing source files.

Limitations and notes

The server depends on a working Godot installation and a valid project path. If Godot cannot be located, configure GODOT_PATH; if the project path does not contain project.godot, project operations will fail. Connection problems may require confirming that the MCP process is running and restarting the AI client.

The material does not document remote hosting, API credentials, OAuth, or a Godot version range beyond the specific Godot 4.4+ requirement for UID operations. The repository is released under the MIT license.