godot

Godot MCP is a middleware server that exposes a standardized MCP interface to control and interact with Godot projects. It enables AI assistants and tools to launch the Godot editor, run projects, manage scenes and nodes, load assets, and retrieve debugging output and project metadata. With this server, you can issue high-level commands like launching a project, creating scenes, adding nodes, loading textures, and exporting assets, while receiving structured feedback and logs from the actual Godot process. This enables seamless integration with AI assistants such as Cline, Cursor, and Claude, providing real-time visibility into Godot output and robust automation capabilities for scene management and project operations.

To use the server, run it through your chosen MCP configuration (e.g., Cline or Cursor). The server exposes commands such as launch_editor, run_project, get_debug_output, stop_project, get_godot_version, list_projects, and a suite of scene management operations (create_scene, add_node, edit_node, remove_node, load_sprite, export_mesh_library, save_scene). Each command is designed to be self-descriptive and returns structured results including success status, messages, and relevant data (e.g., version info, project paths, or scene details). Ensure you have Godot installed and accessible via GODOT_PATH, and that the Node.js runtime is available since this server runs on Node.js.

Prerequisites:

• Node.js and npm installed
• Godot Engine installed and accessible via GODOT_PATH
• A supported MCP client (e.g., Cline or Cursor) to configure and use the server

Installation steps:

1. Clone the repository git clone https://github.com/bradypp/godot-mcp.git cd godot-mcp

2. Install dependencies npm install

3. Build the project npm run build

4. Run the MCP server (example using Node.js runtime directly or via your MCP configuration) node build/index.js

5. Configure your MCP client to point to the server using the provided mcp_config snippet from the README (adapt path to your environment).

Tips and common issues:

• Ensure GODOT_PATH points to a valid Godot executable; if not set, the server may auto-detect or fail to perform certain operations.
• If you encounter read-only mode issues, double-check the READ_ONLY env var (set to true to restrict operations).
• The default configuration lists a comprehensive set of auto-approve actions; adjust autoApprove according to your security policy and workflow.
• Use the get_godot_version tool to verify compatibility with your Godot project before performing complex scene operations.
• When running in a CI environment, prefer read-only mode for analysis tasks to avoid unintended modifications.