godot-mcp
MCP server for interfacing with Godot game engine. Provides tools for launching the editor, running projects, and capturing debug output.
Runssource: GitHubJavaScriptMITcommit 1209744fad78
JavaScript, MIT licensed. The project labels itself: ai, godot and mcp.
godot-mcp runs. An Argusic agent installed it in 0.5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Install builds cleanly. MCP server starts and responds to all 13 tools. Real Godot v4.3-stable binary was downloaded and used for verification, 10 tools work end-to-end, 2 (load_sprite) fail due to headless rendering limitation, and 2 (get_uid, update_project_uids) correctly report needing Godot 4.4+.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- require('fs') call in ESM module causes runtime warning in get_project_info4 minutes
- load_sprite tool fails with real Godot headless: image loader needs rendering context
- Install time
- under a minute
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- npm run build exited 0; MCP server stdio exchange tested 12 tools: get_godot_version returned '4.3.stable.official.77dcf97d8', list_projects found test project, get_project_info returned correct project name/structure, create_scene produced valid .tscn file (cat verified), add_node added Sprite2D node (cat verified), save_scene succeeded, run_project started Godot process (stop_project stopped it), launch_editor started editor mode, export_mesh_library executed (0 meshes for 2D scene, expected).
- Model tokens used
- 85,593
- Exact commit tested
- 1209744fad78
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
exec /bin/sh -lc 'cd /work/repo && npm run build 2>&1' in /work/repo succeeded in 2943ms: > [email protected] build > tsc && node scripts/build.js Successfully copied godot_operations.gd to build/scripts Build scripts completed successfully! Now let me compile the final report. 2026-09-29T10:27:46.991451Z ERROR codex_core::session: failed to record rollout items: thread 01a0e… tokens used 85,593 Now let me compile the final report.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 0.5 minutes, faster than the median of the 63 comparable projects Argusic has measured.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 64 ai projects Argusic has installed and timed, godot-mcp was the 6th fastest to reach a running state, and 49 of 64 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 0.5 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/godot-mcp)Questions
- Does godot-mcp run?
- Yes. godot-mcp runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test godot-mcp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1209744fad78. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test godot-mcp?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does godot-mcp take to install?
- 0.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does godot-mcp need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing godot-mcp?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does godot-mcp compare with the alternatives?
- Of the 64 ai projects Argusic has installed and timed, godot-mcp was the 6th fastest to reach a running state, and 49 of 64 reached one at all.
- Where is the evidence for godot-mcp?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.