Better Godot MCP

What n24q02m/better-godot-mcp MCP server does

n24q02m/better-godot-mcp MCP server gives an MCP-compatible AI client structured access to a local Godot 4.x project. Its tool groups cover project metadata and settings, .tscn scene files, scene-tree nodes, GDScript files, resources, signals, input mappings, animations, TileMaps, shaders, physics configuration, audio buses, navigation objects, and UI controls. A help tool provides detailed documentation for individual tools.

The server is suited to workflows where an agent needs to make repeatable project changes rather than only generate snippets. For example, an agent can create a scene, add or rename nodes, attach a script, configure input actions, and update related resources through separate structured operations.

How it works

The n24q02m/better-godot-mcp MCP server runs over stdio by default. It works directly against files in the local Godot project, so file-oriented operations do not require the Godot editor or engine to be running. Each operation can receive a project_path; alternatively, a default path can be supplied with GODOT_PROJECT_PATH.

The project tool includes metadata and version queries, settings reads and writes, and run, stop, and export actions. The editor tool can launch Godot and report editor status. These engine-dependent actions require a detected Godot binary. The README states that detection accepts Godot 4.1 or newer, with live compatibility verified against Godot 4.7.1 stable.

Setup and configuration

Install the n24q02m/better-godot-mcp MCP server with npm:

npx -y @n24q02m/better-godot-mcp@latest

Add the command to the MCP client configuration and optionally set GODOT_PROJECT_PATH to the project directory. If that variable is omitted, pass project_path with each tool call. The repository also provides a Docker image, which requires mounting the Godot project into the container so the server can access its files.

No account, relay, API key, or other credential is required. The repository documents setup for clients including Cursor and Windsurf, and the server can also be configured through a general mcp.json file.

Tools and capabilities

The listed composite tool groups provide these operations:

• Inspect, run, stop, export, and configure a project.
• Create, list, inspect, duplicate, delete, and select main scenes.
• Add, remove, rename, and edit node properties in a scene tree.
• Create, read, write, attach, list, and delete GDScript files.
• Manage resources, signals, input actions, and input events.
• Create animation players, animations, tracks, and keyframes.
• Create TileSets, add sources, set tiles, and paint TileMaps.
• Create and edit shaders using Godot 4 syntax.
• Configure collision layers, physics bodies, audio buses, navigation, and UI controls.

Limitations and notes

The server targets Godot 4.x rather than documenting compatibility with Godot 3.x. File manipulation can work without Godot installed, but editor, run, stop, and export operations depend on a usable Godot binary. Because the server reads and writes local project files directly, the configured path and filesystem permissions determine which project it can modify. The README identifies the default transport as stdio; it does not describe a hosted remote endpoint or credential-based authentication.