A harness for driving a Godot 4 project from an agent: addons, runtime bridge, MCP server, CLI.
io.github.Aureliolo/gdharness — MCP Server
A harness for driving a Godot 4 project from an agent. It provides addons, a runtime bridge, an MCP server, and a CLI to support agent-based control of the project. The repository description focuses on integrating Godot 4 workflows with agent execution via these components.
🛠️ Key Features
Harness for driving a Godot 4 project from an agent
Includes addons
Includes a runtime bridge
Provides an MCP server
Includes a CLI
🚀 Use Cases
Using an agent to drive a Godot 4 project
Running Godot 4-related actions through an MCP server and CLI
Bridging agent execution with Godot runtime via a runtime bridge
⚡ Developer Benefits
Clear separation of components: addons, runtime bridge, MCP server, and CLI
Supports agent integration with Godot 4 through the provided harness
⚠️ Limitations
Available details only describe the harness components; no additional capabilities, configuration options, or tool count information is provided.
An agent cannot see a running game. It reads your scripts and guesses at the rest: whether the
button is on screen, whether the panel updated, whether that error mattered.
gdharness is an MCP server and four Godot addons. Through them the agent asks the open editor and
the running game what the screen says and where a control is. It can also ask what a property holds
now, what the console printed, and what broke on which line.
Install
Hand this to your agent:
text
Install gdharness here by following https://aureliolo.github.io/gdharness/agent.md,
then tell me what it asked you to recommend back to me.
editor_run {"op":"start","projectPath":"C:/games/shop"}
runtime_inspect {"op":"find","says":"Buy"}// the button, by the word on it
runtime_input {"op":"click","nodePath":"/root/Shop/Ledger/BuyButton"}
runtime_inspect {"op":"text","nodePath":"/root/Shop/Ledger"}// what the panel says now
editor_output {"projectPath":"C:/games/shop"}// errors and warnings, with backtraces
The open editor plays the game, so you can set a breakpoint and read the variables in scope when it
stops.
Writes answer with what the engine holds afterwards, never an echo of the request. A tool that
cannot answer says which state it is in and what would change it.
At a glance
Needs
Godot 4.7 or newer, Node 22 or newer. Runs under Bun 1.4 too.
Surface
31 tools named domain_verb, 4 godot:// resources and 3 prompts
Reaches
The editor that is open, a game it is playing, and the project on disk
Harnesses
35, written inside the project wherever the harness has a project config
Skill
Written to .agents/skills, with a copy for Claude Code, Kiro and Cline
Install
npm, or a Sigstore-signed archive with an SBOM, SLSA Build Level 3
Proven
Every tool driven against Godot 4.7.2 in CI, on Windows, Linux and macOS