Log inSubmit server
Godot Agent Loop logo

Godot Agent Loop

Godot 4 MCP automation loop for authoring, running, observing, playtesting, and verifying game projects.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Godot Agent Loop

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": {
    "godot-agent-loop": {
      "command": "npx",
      "args": [
        "-y",
        "@beremaran/godot-agent-loop"
      ]
    }
  }
}

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

Automated check passed— started and listed 16 tools correctly (4d ago).

Overview

Godot Agent Loop MCP server connects MCP-compatible AI assistants to Godot 4 projects through a task-oriented automation loop. It can start and stop projects, inspect runtime state, capture screenshots and diagnostics, send structured player input, edit scenes through the attached editor, and run verification checks. Use it when an agent needs evidence from a running game rather than only file-level code changes. The default surface exposes 16 core tools, while additional capabilities are discoverable through catalog and dispatch tools.

Use cases

  • Build and validate a Godot 4 prototype
  • Run deterministic game playtests
  • Inspect runtime errors and scene state
  • Verify project behavior and export readiness
  • Check Godot .NET project builds

Key features

  • Godot 4 project lifecycle control
  • Runtime screenshots and diagnostics
  • Structured game input and scenarios
  • Editor scene transactions with undo support
  • Project, integrity, and export verification
  • Discoverable extended tool catalog

Tools16

What Godot Agent Loop lets your agent do. Expand a tool for its parameters.

Verified live~5.2k tokens of context

Security & health

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

ActiveLast checked 2d ago

Recent health check succeeded.

6/6 checks healthy over the last 40d

What it can do

From the 16 tools this server returned when we ran it; 16 declare their own safety hints.

Runs commands · 1Can delete or modify data · 3Makes network requests · 1Read-only tools · 13
Network at startup3 connections
Files written at startupNone
Install scriptsprepare
npm provenanceSigned build
Package age101 days
Maintainers1

Observed 2026-10-24 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · @beremaran/godot-agent-loop (npm)

Adoption & maintenance

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

GitHub stars10Stargazers on the source repository.
npm downloads849Package downloads in the last 30 days.
Last commit9d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed16Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Godot Agent Loop works

What the Godot Agent Loop MCP server does

Godot Agent Loop MCP server gives an MCP client a bounded workflow for working with Godot 4 projects: author, validate, run, observe, playtest, verify, and refine. It is intended for projects using Godot 4.7 or later, with Godot 4.7 as the current compatibility floor and primary target.

The default core surface contains 16 tools. These cover project lifecycle control, editor sessions, compound scene transactions, runtime observation, structured interaction, waiting, project tests, and verification. Coding agents are expected to use their own file tools for direct edits to GDScript, scenes, resources, and project settings, then use this server to run and assess the result.

How it works

An MCP client launches the server through Node.js and points it at a Godot project directory, including an empty directory for a new project. The server can launch and stop the game, collect logs and errors, inspect the scene tree and UI, retrieve node details, and capture screenshots. It can also compose mouse, keyboard, drag, scroll, touch, and gamepad actions into deterministic scenarios.

Godot Agent Loop MCP server keeps the default tool surface deliberately small. Additional capabilities are found with the read-only godot_catalog tool and invoked with godot_call. These include extra input methods, performance and visual observations, camera and audio checks, editor controls, import and export checks, add-on tooling, and optional runtime reflection.

With an editor attached, editor_session can find the matching project and editor_transaction can apply compound, undoable scene changes through Godot's editor undo system. Privileged reflection and code execution are disabled unless explicitly enabled, and the editor includes a human pause control.

Setup and configuration

Install Node.js 22 or newer and Godot 4.7 or newer. Start the server with an MCP client using:

Terminal
claude mcp add godot-agent-loop -- npx -y @beremaran/godot-agent-loop

The README specifically documents use with Claude Code, Cline, and Cursor, while other MCP clients may provide their own configuration format. A .NET SDK 8.0 or newer and the Godot .NET build are needed only for .NET project verification with verify_dotnet_project.

Rendering and screenshot workflows require a headed rendering context. On Linux, this can be a desktop display or Xvfb; display-less sessions fail with remediation guidance. Privileged runtime operations are intended for trusted localhost development.

Tools and capabilities

  • Start and stop Godot projects.
  • Inspect screenshots, scene trees, UI state, node information, logs, and errors.
  • Playtest with structured keyboard, mouse, touch, scroll, drag, and gamepad input.
  • Wait for conditions and run native, GUT, or GdUnit4 project tests.
  • Verify runtime behavior, project integrity, and export readiness.
  • Inspect, build, restore, and run Godot .NET projects when the required SDK is installed.
  • Use visual-regression comparisons with baselines, masks, and retained differences.

Limitations and notes

The project does not claim full debugger automation, native extension builds, or unrestricted engine control. Windows support covers portable process, input, window-query, and teardown workflows, but not editor UI, rendering, or exports. Linux editor attachment is verified in CI, and a headed macOS 4.7.1 editor workflow is documented. Export verification claims cover Linux release and debug templates rather than every target platform.

Godot Agent Loop MCP server uses response size caps and deterministic pagination for large results. Runtime injection is transient; projects that need a persistent editor connection can use the optional persistent editor add-on. The documented evidence and integration coverage should be reviewed before relying on a workflow outside the verified support boundary.

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 Godot Agent Loop

Godot Agent Loop is an MCP server that connects AI assistants to Godot 4 projects for authoring, runtime control, observation, playtesting, and verification. Its main tools include project lifecycle commands, editor sessions, screenshots, scene and UI inspection, structured game input, diagnostics, project tests, and independent verification.

Install Node.js 22 or newer and add it to an MCP client with `claude mcp add godot-agent-loop -- npx -y @beremaran/godot-agent-loop`. You also need Godot 4.7 or newer. The client can then point the agent at a Godot project directory.

Yes, Cursor is named as a supported MCP client in the README. Configure the server using Cursor's MCP setup, then provide a Godot project directory. The same server can expose its default core tools and discover additional tools through `godot_catalog` and `godot_call`.

Godot 4.7 or newer is required, with 4.7 listed as the compatibility floor and primary target. The documented support boundary varies by platform: Linux has retained headed CI coverage, macOS has an attached-editor workflow on 4.7.1, and Windows support is limited to specified portable workflows.

Yes, it can launch a project, inspect runtime state, capture screenshots, collect logs and errors, send structured player input, wait for conditions, and run project tests. `verify_project` provides bounded runtime evidence, while visual comparisons and export-readiness checks cover additional verification needs.

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 PreviewGodot Agent Loop AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/godot-agent-loop?style=directory)](https://allmcps.com/mcp/godot-agent-loop)
HTML Embed
<a href="https://allmcps.com/mcp/godot-agent-loop"><img src="https://allmcps.com/api/badge/godot-agent-loop?style=directory" alt="Godot Agent Loop on AllMCPs" /></a>