coding-solo/godot-mcp

Godot MCP is a server that lets AI coding assistants control the Godot game engine directly. MCP stands for Model Context Protocol, which is a standard that tools like Claude, Cursor, and Cline use to communicate with external programs. By connecting this server to one of those AI tools, you can ask the AI to open a Godot project, run it, read the output, and make changes, without you having to switch windows and copy-paste error messages back and forth. Godot is a free, open-source game engine used to make 2D and 3D games. If you are building a game in Godot and using an AI assistant to help write code, the usual friction is that the AI cannot see what happens when the game actually runs. Godot MCP closes that gap by giving the AI a live connection to Godot. The AI can launch the editor, start the game in debug mode, capture the console output and any error messages, and stop the game when it is done, all from within the conversation. Beyond running the project, the server also exposes scene management tools. The AI can create new scenes, add nodes to existing ones, set properties on those nodes, load sprites and textures, and export 3D scene data as resources for use in grid-based maps. For Godot 4.4 and newer, it also handles UID management, which is an internal file referencing system that Godot uses to keep track of assets when files are moved. Setup is a single command. For Claude Code, you run one line in the terminal to register the MCP server, then restart. Cursor and Cline have their own config files where you add a short JSON block. Node.js 18 or newer must be installed alongside Godot itself. The README describes an architecture split between simple commands (which call Godot directly via its CLI) and more complex operations (which use a bundled GDScript that Godot runs as a headless process).