Godot

Godot MCP provides an interface for Claude (or other MCP-enabled assistants) to interact with your Godot project directly from text prompts. The server exposes a range of commands to inspect and modify your project, including Node commands for manipulating the scene tree and node properties, Script commands for editing GDScript files, Scene commands for reading and creating scenes, Project commands for settings and resources, and Editor commands to control the editor lifecycle. Once the MCP server is running and Claude Desktop is configured to connect via the provided transport, you can issue prompts like reading the current script, generating or modifying scenes, or analyzing project scripts, all through natural language with direct edits applied in Godot.

To use it, run the server (via node) and configure Claude Desktop to point to the server as shown in the example configuration. In Claude, you send prompts prefixed with the MCP server name (for example, @mcp godot-mcp read godot://script/current) and the assistant will translate that into the appropriate MCP command, fetch results, and apply changes back to your Godot project as needed. The available resource endpoints (godot://script/current, godot://scene/current, godot://project/info) guide what data you can request or modify and help you craft precise prompts for tasks like generating a new scene, adjusting node properties, or updating scripts.

Prerequisites:

• Node.js and npm installed on your development machine
• Git to clone the repository

Step-by-step:

1. Clone the repository and install dependencies git clone https://github.com/ee0pdt/godot-mcp.git cd godot-mcp

2. Install server dependencies and build cd server npm install npm run build

3. Return to the project root and prepare Claude Desktop configuration (example given in README) cd ..

4. Configure Claude Desktop to connect to the MCP server (refer to README for details):

   • Create or edit claude_desktop_config.json and set: { "mcpServers": { "godot-mcp": { "command": "node", "args": [ "PATH_TO_YOUR_PROJECT/server/dist/index.js" ], "env": { "MCP_TRANSPORT": "stdio" } } } }

5. Start the server (via Claude Desktop) or run the server manually: node PATH_TO_YOUR_PROJECT/server/dist/index.js

6. Open Godot and load the example project, ensuring the MCP plugin is enabled as described in the README.

Prerequisites recap:

• Node.js and npm
• Access to a Godot project with the MCP plugin setup guide followed
• Claude Desktop configured to load the provided MCP server entrypoint

Tips and notes:

• Ensure MCP_TRANSPORT is set to stdio to communicate with Claude Desktop as shown in the config example.
• Absolute paths are required in the Claude Desktop config (PATH_TO_YOUR_PROJECT).
• If the server isn’t responding, verify the server process is running and that the Claude Desktop config points to the correct index.js file.
• Enable the Godot MCP plugin in your Godot project after import as described in the README to ensure changes can be applied.
• When testing scripts or scenes, use specific endpoints like godot://script/current or godot://scene/current to guide prompts and reduce ambiguity.
• If you modify server code, rebuild with npm run build before restarting Claude Desktop.