Toolbench MCP server
Godot MCP (Coding-Solo)
CJM Tested
An MCP server that lets an AI agent create scenes, add nodes and run a Godot project.
- CJM score
- 8.4/10
- Last tested
- 2026-10-15
- Info checked
- 2026-10-15
Overview
What it is
An open source Model Context Protocol server that wraps the Godot binary. An MCP client such as Claude Code, Cursor or Cline can call its tools to read project info, create scenes, add nodes, save, run the project and read the debug output.
Who it is for
Godot developers who already use an MCP-capable agent and want it to touch the editor and see runtime errors instead of guessing.
Hands-on test 2026-10-15
What we ran
Version: godot-mcp 0.1.0 (commit 1209744) with Godot 4.5 stable, Linux x86_64. Cloned the repo, npm install and npm run build, then drove it over stdio with a small JSON-RPC script acting as the MCP client, with GODOT_PATH set to the Godot 4.5 binary.
Through the MCP server: report the Godot version and project info, create scenes/player.tscn with a CharacterBody2D root, add a CollisionShape2D and a Camera2D, save the scene, run it and read back the debug output.Result
- tools/list returned 14 tools. get_godot_version and get_project_info answered in under 0.1 s.
- create_scene, add_node (CollisionShape2D and Camera2D) and save_scene each took under 1 s and wrote a valid Godot 4 .tscn.
- run_project with no display: reported success, but Godot exited at once and get_debug_output said no process was running. Easy to miss.
- run_project with a virtual display: the project ran, and get_debug_output returned stdout and errors as JSON, including the renderer falling back from Vulkan to Compatibility. stop_project returned the final log.
Score
8.4 out of 10
| Area | Score |
|---|---|
| Setup | 8/10 |
| Output | 8/10 |
| Speed | 9/10 |
| Value | 10/10 |
| Game-dev fit | 7/10 |
We tested the server directly, not through a specific agent. Results inside Claude Code or Cline will also depend on the agent. The overall score is the plain average of the five areas.
Engines
Engine compatibility
Only engines we ran the tool with are marked as tested. Everything else says not tested yet, even where the vendor claims support.
| Engine | Status |
|---|---|
| Godot | Tested here |
| Unreal | Not supported |
| Unity | Not supported |
| Roblox | Not supported |
| Minecraft | Not supported |
Pricing
What it costs
Free and open source (MIT). Checked on the GitHub repository, 15 October 2026.
Prices change often. Check the vendor page before you buy.
Pros and cons
Good
- All 14 tools listed over stdio and the scene tools worked first try
- Scene files it wrote are clean, valid Godot 4 .tscn
- get_debug_output returns engine errors as structured JSON an agent can read
Watch out
- run_project starts a windowed Godot, so on a server with no display it exits and reports no process
- No tool to attach or edit a script, so an agent still writes .gd files on its own
- Debug output includes noisy driver warnings on machines without Vulkan
Alternatives