godot-mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
godot-mcp
An MCP server that lets AI agents like Claude Code run your Godot game, look at it, and play it.
Agents can already read and write .gd and .tscn files on their own. What they can't do is see what happens when the game runs. This closes that loop: start the game, take a screenshot, inspect the live scene tree, press inputs, read the errors.
Tools
Tool | What it does |
| Starts the project (or a specific scene) and waits until it is connected |
| Stops the game |
| Latest stdout/stderr lines: |
| Screenshot of the running game |
| Live node tree with types, scripts, positions and hidden nodes |
| Presses an Input Map action for a given time |
Related MCP server: godot-mcp
How it works
agent <--stdio--> godot-mcp server <--WebSocket--> game (GodotMCP autoload)
|
+-- starts godot --path <project> as a child processThe server starts Godot itself and reads its output. When the game boots, the GodotMCP autoload connects back to the server over a WebSocket on 127.0.0.1 using a port and token passed on the command line. Without those arguments the autoload does nothing, and it is disabled in release builds.
Requirements
Godot 4 (tested on 4.7.2)
Node.js 20 or newer
Setup
Build the server:
git clone https://github.com/CyberIce2077/godot-mcp.git ~/projects/godot-mcp cd ~/projects/godot-mcp npm installCopy
addons/godot_mcpinto your game'saddons/folder, then enable Godot MCP under Project > Project Settings > Plugins. Enabling it registers theGodotMCPautoload.Add the server to Claude Code from your game's folder:
claude mcp add godot -- node ~/projects/godot-mcp/dist/index.js
Configuration
Variable | Default | |
|
| Godot executable |
| current directory | Folder containing |
For example:
claude mcp add godot -e GODOT_PROJECT=/path/to/game -e GODOT_PATH=/Applications/Godot.app/Contents/MacOS/Godot -- node ~/projects/godot-mcp/dist/index.jsLimitations
The game runs in a normal window. Godot's headless mode has no renderer, so screenshots would be blank.
Only one game at a time per server.
No editor integration yet: the agent edits scenes and scripts as files.
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
AI game maker: build, run, screenshot and play-test Godot and retro console games in a live project
Drive real devices from your AI Coding tool. Embed a client SDK (Unity, Godot, Flutter, iOS/macOS, Android, React Native, Web) in your app, then capture screenshots, traverse the UI tree, inject taps and key events, and run automated test tasks on the physical device over a secure relay.
Control a real browser from AI agents: navigate, click, type, screenshot, read the page.
Drive a live Cinevva game session: edit game files, import CC0 assets, preview changes.
Related MCP Servers
- AlicenseBqualityCmaintenanceEnables AI agents to inspect, modify, run, and debug Godot projects, including scene and script analysis, editor and project management, and visual verification through screenshots.2210 npm14MIT
- AlicenseAqualityCmaintenanceEnables AI agents to launch and control the Godot game engine, run projects, capture debug output, and manage scenes and project configurations.14194 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to read and edit Godot 4.x scenes and resources, introspect the class API, run the game in a managed headless process with frame stepping, input injection and screenshots, validate scripts, and diagnose code via a built-in GDScript LSP plus a bridge to an already open editor.23MIT
- AlicenseBqualityBmaintenanceEnables AI agents to interact with the Godot game engine by launching the editor, running projects, capturing debug output, inspecting and editing scenes, running tests, and observing runtime behavior for an iterative game-making loop.32MIT