What it does
gdharness lets an agent ask the open Godot editor and the running game what is on screen, where a control is, what a property holds now, what the console printed, and what failed on which line. Write operations report the state the engine holds afterwards rather than echoing the request. The server exposes 31 tools, 4 godot:// resources and 3 prompts, and reaches the open editor, a game being played, and the project on disk. While the editor plays the game, a breakpoint can be set and the variables in scope read when it stops.
It is useful when an agent needs to check UI state or runtime behaviour in a Godot project instead of inferring it from scripts alone. It supports 35 harnesses, writing configuration inside the project where the harness has a project config. A skill file is written to .agents/skills, with copies for Claude Code, Kiro and Cline.
Installation is available through npm or as a Sigstore-signed archive that includes an SBOM and SLSA Build Level 3 provenance. Every tool was run against Godot 4.7.2 in CI on Windows, Linux and macOS. The project is at version line 1.x, and each release is a patch. It is a fork of GoPeak; the original MCP server is godot-mcp by Solomon Elias, and GoPeak is by HaD0Yun. It is not affiliated with the Godot Foundation.
Limitations and requirements
Requires Godot 4.7 or newer and Node 22 or newer; it also runs under Bun 1.4. Godot versions before 4.7 are not tested.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 17 Nov 2026 · its page on the source
io.github.Aureliolo/gdharness
A harness for driving a Godot 4 project from an agent: addons, runtime bridge, MCP server, CLI.
v1.3.112As shown on registry.modelcontextprotocol.io when we last read it