gdharness
A harness for driving a Godot 4 project from an agent: editor addons, a runtime bridge into the running game, an MCP server in front of them, and a CLI that installs and diagnoses the Godot side.
No outside reports on file
This tool gives an AI agent significant control over your Godot projects and running games, so use it only with trusted agents and keep your projects backed up.
Based on public adoption and transparency signals as of Oct 25, 2026. Our opinion, not a code audit or security guarantee.
What it can access
- Local filesNo local folder access notedLOW
- Command executionNo shell command runner notedLOW
- Network reachConnects to outside service APINOTED
- CredentialsNo API token requiredLOW
- Package sourcenpm (gdharness)PUBLIC
Inferred from this listing’s public package details and description. Check the project’s source before installing.
Install
npx -y gdharnessEverything known
We found nothing about this project in the sources we read (last checked 2026-10-30). That does not mean it has no problems.
0 incidents · 0 advisories · 0 news articles · 0 community threads · checked 2026-10-30
Popularity grade: C (from public signals such as stars and downloads, not a code review). Graded 2026-10-25.
Sources we read: OSV, GitHub Advisory Database, CISA Known Exploited Vulnerabilities, 44 security news feeds and our incident library. Last checked 2026-10-30.
About Gdharness
gdharness is a bridge that lets AI agents control and interact with Godot 4 game projects. It includes editor add-ons, a runtime connection to running games, an MCP server, and command-line tools to set everything up and troubleshoot.
Who it’s for
Developers who want to use AI agents to help build, test, or automate Godot 4 games. This is useful for developers exploring agent-assisted game development workflows.
Alternatives
- Godot REST API (built-in): Godot's native HTTP server for remote control, no third-party dependency.
- godot-python: Allows Python scripting in Godot, useful for agent integration but requires careful sandboxing.
- Custom MCP servers: Build your own tool-specific MCP server tailored to your game's needs.
- Unreal Pixel Streaming + agents: If using Unreal Engine instead, similar remote control setups exist.
Setup
Check these steps against the project’s own instructions before running anything.
Install via npm:
npm install -g gdharness
Then follow the project's README at https://github.com/Aureliolo/gdharness (opens external site) for Godot-side setup and MCP server configuration.
Why this grade
Signal-based grade (3/7 points): listed in several sources, public source code. This reflects adoption and transparency, not a code review.
Popularity and upkeep
- GitHub stars
- 26
- Weekly npm downloads
- 7.7k
- Listing last refreshed
- 2026-10-29
These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.
Risks to watch for
- Game project access: The tool can read and modify Godot project files on your computer, so any malicious code in gdharness could alter your game assets or code.
- Running game control: It connects to live Godot processes, giving an AI agent the ability to execute game logic, spawn objects, or trigger game events.
- File system exposure: The CLI and editor add-ons touch your file system during installation and diagnosis, potentially exposing paths to other projects.
- Tricky configuration: If you misconfigure permissions or network settings, the agent could access more than intended.
- Supply chain: Like any npm package, gdharness could theoretically be compromised, though it has a modest download base (2863 weekly).
How to lower the risk
Least-privilege permissions
- Run gdharness in a separate user account if possible.
- Limit the agent's ability to modify core game files.
Network isolation
- Keep the MCP server connection local to your machine when testing.
- Don't expose the MCP server port to untrusted networks.
Monitoring
- Watch for unexpected file changes in your Godot projects.
- Review agent requests before they modify game logic.
Red flags to watch for
- Commands that try to access unrelated directories on your computer.
- Requests to install additional packages or tools without clear reason.
Questions
How do I install Gdharness?
Run npx -y gdharness in your terminal, or add the server entry to your claude_desktop_config.json or .cursor/mcp.json as shown in the Setup section on this page. Full setup docs and environment variables are in github.com/Aureliolo/gdharness.
Are there security reports about Gdharness?
No reports found for this package in our research (last checked 2026-10-30). Gdharness currently holds Grade C (Moderate risk signals) based on public adoption and transparency signals. Key risk areas to watch include game project access, running game control, file system exposure.
Is Gdharness actively maintained?
Gdharness has 26 GitHub stars and 7.7k weekly npm downloads. Our directory data was last refreshed on 2026-10-29. Check recent commit activity, release tags, and open issues at github.com/Aureliolo/gdharness before pinning it in production.
What are alternatives to Gdharness?
Notable alternatives to Gdharness include Godot REST API, godot-python (Allows Python scripting in Godot, useful for agent integration but requires careful sandboxing), Custom MCP servers (Build your own tool-specific MCP server tailored to your game's needs), Unreal Pixel Streaming + agents (If using Unreal Engine instead, similar remote control setups exist). You can also compare Gdharness side by side with other MCP servers in the Related tools section on this page.
README badge and team notes
Maintain or use Gdharness? Show its live grade in your GitHub README, docs site, or run a check from the terminal before you install.
GitHub README Markdown:
[](https://agentarmorhq.com/skills/aureliolo-gdharness)HTML embed:
<a href="https://agentarmorhq.com/skills/aureliolo-gdharness"><img src="https://agentarmorhq.com/api/badge/aureliolo-gdharness" alt="AgentArmorHQ Risk Grade for Gdharness" height="20" /></a>Terminal check:
curl -fsSL https://agentarmorhq.com/api/cli | node --input-type=module - check "aureliolo-gdharness"Share with your security lead
Need sign-off to use gdharness? Copy this note for Slack, a ticket or a pull request.
### AgentArmorHQ Security Review Memo: gdharness
- **Listing URL:** https://agentarmorhq.com/skills/aureliolo-gdharness
- **Type:** App connector
- **Risk Grade:** Grade C (Moderate risk signals)
- **Outside Security Advisories on File:** 0
- **Public Adoption:** 26 GitHub stars, 7.7k weekly npm downloads
#### Permission & Blast-Radius Signals
- **Local files:** No local folder access noted
- **Command execution:** No shell command runner noted
- **Network reach:** Connects to outside service API
- **Credentials:** No API token required
- **Package source:** npm (gdharness)
#### Recommended Hardened Setup
- **Command:** `npx -y --ignore-scripts gdharness`
- **Controls:** Pin an exact version in `.mcp.json`, scope access to a single workspace folder, and use a least-privilege read-only token where supported.
_Based on public adoption and transparency signals as of Oct 25, 2026. Our opinion, not a code audit or security guarantee._Key facts
- Type
- App connector
- Publisher
- Aureliolo
- Source code
- github.com/Aureliolo/gdharness
- Install command
- npm install gdharness
- Est. context load
- ~750 tokens / turn (~4 tool schemas, 0.38% of 200k context)
- Popularity
- 26 GitHub stars, 7.7k weekly npm downloads
- Last updated
- 2026-10-29
- Last graded
- 2026-10-25
Community
Discussions for Gdharness
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.
Check before you install, in Claude
Your assistant answers Block, Review or No known issues for any package before it installs it.
Get this check inside Claude