Godot Agent Loop

A local MCP server that gives an AI assistant a full loop for Godot 4 game projects: author, run, observe, playtest and verify.

What you can do

Discover and dispatch hidden capabilities through a catalog and generic call tool, with a lean core surface of 16 advertised tools out of a larger catalog of 56 total tools (16 core plus 40 hidden). Manage the project lifecycle: run, stop and test Godot projects, including native, GUT and GdUnit4 runners and .NET build workflows. Observe a running game: screenshots, scene tree, UI, node info, errors and logs. Playtest with structured scenarios and waits, plus input primitives such as mouse, keyboard, touch and gamepad. Drive the editor session and apply undoable compound scene transactions, and verify projects with bounded assertions, export readiness and integrity analysis.

When to use it

Useful when an assistant is building, debugging or testing a Godot 4 game project and needs to launch it, watch it run, simulate player input and check results rather than only editing files. Suited to local developer workflows on a desktop with a rendering context.

Requirements

Runs locally over stdio via npx, so Node.js 22 or later is needed. Requires Godot Engine 4.7 or later, with GODOT_PATH optionally set to the executable. Optional .NET SDK 8 and the Godot .NET build for C# projects. A desktop display or Xvfb is needed for running games and screenshots. Optional editor addon must be copied into the project and enabled, then Godot restarted.