Godot MCP - Full Control is a comprehensive MCP server that exposes a broad suite of Godot engine controls to an AI assistant. It provides 149 tools for runtime inspection, scene manipulation, project management, and runtime code execution within a running Godot project. Tools cover runtime node inspection, property reads/writes, dynamic scene modifications, signal management, animation and tween controls, file I/O, and even headless scene operations for parsing and editing .tscn scene files without starting a game. You can use these tools to script complex workflows, automate game testing, or build AI-assisted development workflows that interact with the Godot engine in real time. The server is built on TypeScript and extends the original godot-mcp, adding advanced capabilities like game_eval for executing GDScript and full node introspection via game_get_node_info.

Prerequisites:

• Node.js (v14+ recommended)
• npm or yarn

Step-by-step installation:

1. Create a workspace directory and navigate into it mkdir godot-mcp-workspace cd godot-mcp-workspace

2. Install the MCP server package from npm (assuming the package name is godot-mcp) npm install godot-mcp

   or using yarn

   yarn add godot-mcp

3. Run the MCP server (using npx integration as defined in mcp_config) npx -y godot-mcp

4. (Optional) Configure environment variables as needed GMCP_API_KEY=your-api-key GMCP_DEBUG=false npx -y godot-mcp

5. Verify the server starts and exposes the MCP endpoints

   • Ensure your AI client can connect to the MCP server on the configured port.

If you prefer a local build or a different launcher, refer to the package.json scripts in the repository for alternative start commands.

Notes and tips:

• This MCP server exposes a large toolbox of Godot interactions; start with read-only checks (game_get_property, game_get_node_info) to understand the node trees before performing write operations.
• When using runtime code execution (game_eval), ensure you handle potential exceptions from GDScript execution and sandbox appropriately.
• Be mindful of performance: many tools (like listing all nodes or querying large scene trees) can be expensive on large projects.
• Use the headless scene operations (read_scene, modify_scene_node, attach_script) to inspect or modify scenes without launching the game.
• Environment variables: GMCP_API_KEY may be required for certain features; GMCP_DEBUG can help with verbose logs during setup.
• If you encounter connection issues, verify the MCP server is listening on the expected host/port and that the client uses compatible MCP protocol versions.