Log inSubmit server
Gdharness logo

Gdharness

Drive Godot 4 projects through MCP tools that inspect runtime state, send input, run the editor, and read diagnostics.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Gdharness

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "gdharness": {
      "command": "npx",
      "args": [
        "-y",
        "gdharness"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

gdharness MCP server connects an AI agent to an open Godot editor, the game it is running, and the project on disk. Its tools can start projects, inspect visible text and scene nodes, send runtime input, read properties, and retrieve console errors with backtraces. The server uses Godot addons and a runtime bridge so responses come from the engine rather than being echoed from requests. Reach for gdharness when an agent needs to test or debug a Godot 4 project through observed game state.

Use cases

  • Start a Godot project from an agent
  • Inspect runtime controls by their visible text
  • Send input to scene nodes
  • Read updated UI text after an interaction
  • Collect Godot errors and backtraces

Key features

  • Godot editor and runtime control
  • Runtime text and node inspection
  • Node-targeted input actions
  • Editor warnings, errors, and backtraces
  • 30 MCP tools, four resources, and three prompts
  • Node.js 22+ and Bun 1.4 support

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

10/10 checks healthy over the last 44d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8h ago via OSV.dev · gdharness (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars16Stargazers on the source repository.
npm downloads27kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Gdharness works

What gdharness does

gdharness gives an MCP-compatible agent an interface for driving and inspecting Godot projects. It reaches three parts of a development workflow: the open Godot editor, a game launched by that editor, and files in the project. This lets an agent work from runtime evidence instead of relying only on scripts or inferred UI state.

The package is intended for Godot 4 projects and is made for Godot 4.7 or newer. Older Godot 4 versions may work, but the tested target is 4.7. The project is MIT licensed and is not affiliated with the Godot Foundation.

How it works

The installation places the harness components inside a Godot project where the required project configuration is available. Godot addons and a runtime bridge expose engine state to the MCP process. The MCP server then presents tools, resources, and prompts to an agent.

A typical interaction starts a project through the editor, locates a control by the text it displays, sends an input action to a node, and reads the resulting text or property value. Separate editor output can return warnings, errors, and backtraces. The open editor also provides the debugging context needed to set a breakpoint and inspect variables in scope when execution pauses.

Responses are read back from the engine after an operation. When a tool cannot answer because of the current state, it reports that state and the condition that would allow the operation to proceed.

Setup and configuration

The documented installation paths are the npm package or a signed release archive. The project requires Godot 4.7 or later and Node.js 22 or later; Bun 1.4 is also supported. Installation is performed for the target Godot project, with harness files written inside the project.

The project publishes installation guidance and the complete tool reference through its documentation site. Releases include a software bill of materials, are Sigstore-signed, and use SLSA Build Level 3 release provenance.

Tools and capabilities

The MCP surface contains 30 tools using domain_verb names, four godot:// resources, and three prompts. The demonstrated tool groups include:

  • editor_run for starting the project from the editor.
  • runtime_inspect for finding visible text, reading text, and examining runtime state.
  • runtime_input for interacting with runtime nodes such as buttons.
  • editor_output for collecting project errors, warnings, and backtraces.

Runtime inspection can identify a control by the words it displays or read the text currently held by a node. Input can target a node path such as /root/Hall/Ledger/BuyButton. The broader tool surface covers the editor, running game, and project on disk.

Limitations and notes

The harness depends on a Godot editor and project environment rather than operating as a standalone game automation service. Its tested platform coverage includes Windows, Linux, and macOS, with tools driven against Godot 4.7.2 in continuous integration. Older 4.x releases are not part of that tested target.

The package describes its harness skill as being written to .agents/skills, a location read by major agent harnesses. It also identifies 35 harnesses that can be written inside a project wherever the harness has a project configuration. The project is a reworked fork of GoPeak and earlier Godot MCP work.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Gdharness

gdharness is an MCP server that connects AI agents to an open Godot 4 editor, its running game, and the project on disk. Its main tools start projects, inspect runtime text and nodes, send input to controls, read properties, and collect editor errors, warnings, and backtraces from Godot.

Install gdharness for the target Godot project through npm or a signed release archive. The project requires Godot 4.7 or newer plus Node.js 22 or newer, with Bun 1.4 also supported. Its installation documentation provides the project-specific steps and configuration.

gdharness targets Godot 4.7 and newer. Its tools are tested against Godot 4.7.2 on Windows, Linux, and macOS. Older Godot 4 versions may work, but they are outside the documented tested target.

gdharness can find controls by displayed text, read text from nodes, inspect runtime state, and read properties after interactions. It can also return editor warnings, errors, and backtraces, giving an agent runtime and diagnostic information from the Godot environment.

The project documentation identifies gdharness as an MCP server but does not name Cursor-specific setup. It exposes a standard MCP tool surface with 30 tools, four resources, and three prompts for an MCP client to use.

Related MCP servers

All in Gaming All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGdharness AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/gdharness?style=directory)](https://allmcps.com/mcp/gdharness)
HTML Embed
<a href="https://allmcps.com/mcp/gdharness"><img src="https://allmcps.com/api/badge/gdharness?style=directory" alt="Gdharness on AllMCPs" /></a>