Godot MCP: Complete Setup Guide & Server Comparison (2025)

MCP — the Model Context Protocol — is an open standard for connecting AI applications to external systems. The official docs compare it to "a USB-C port for AI applications": one standardized plug, many devices (modelcontextprotocol.io, accessed Sep 2026).

A Godot MCP server is one of those devices. Plug it into Claude Code, Codex, or Cursor and the agent gains tools to operate the editor directly: launch the Godot editor for a project, execute the project in debug mode, retrieve console output and errors, create scenes with specific root node types, add nodes with custom properties, load sprites into Sprite2D nodes, and — since Godot 4.4 — read and update resource UIDs (Coding-Solo README).

The practical difference is blunt. Without it, you copy AI-suggested GDScript into the editor, run it, read the error, paste the error back. With it, the agent runs the project itself, reads the actual error, and fixes its own output. One loop instead of three.

The editor your AI agent takes over. Screenshot © Juan Linietsky, Ariel Manzur, CC-BY 4.0, via godotengine.org.

The four main implementations, compared

Here's the part that confused everyone until now: "Godot MCP" is not one tool. PulseMCP's directory currently lists 34 servers matching "godot" (pulsemcp.com, accessed Sep 2026). Most are experiments. Four are worth your time.

Why these criteria? A year ago, a Godot developer (who builds one of the servers himself — disclosed) posted a comparison on r/godot that drew 20+ comments. His dimensions: smooth GDScript editing, reading output logs and parse errors, end-to-end testing via screenshots, and tolerance for sloppy node paths like World/Player vs ./World/Player. Real users argued about exactly these. Note the post is a year old and its author sells GDAI MCP — useful dimensions, biased conclusions.

Our take, and we'd argue it: start with Coding-Solo's. It's the #1 ranking repo for a reason — it's a plain Node.js server, so it works with every MCP client without touching your project's toolchain, and its scene/node operations cover the common cases. Pick IvanMurzak's if your project is C#-heavy and you want the 42-tool depth; it shares its MCP stack with Unity-MCP, which shows in the polish. The plugin-based options trade convenience for tighter editor integration — reasonable once you already know you'll use MCP daily.

Installation: five minutes, three prerequisites

Three things must exist first (from the official requirements):

1. Godot Engine, installed locally
2. Node.js 18 or newer, with npm
3. Any MCP-capable AI client

Check with node --version. If it prints anything below v18, upgrade first — the server won't start.

Install and verify

For Claude Code, this is the entire installation:

Restart Claude Code. The Godot tools appear in the agent's tool list. That's the whole step.

For clients that read a JSON config instead, the equivalent is:

When Godot isn't found

If the server can't locate your editor binary, pass the path explicitly:

Set DEBUG=true the same way to get verbose server-side logs — the first thing to try when tools silently fail.

Wiring it into your AI client

This is where existing guides stop, and where most of the search traffic actually sits: people don't ask "what is godot mcp" nearly as often as they ask how to connect it to the client they already use.

Claude Code. Done above — the claude mcp add command registers the server permanently. No JSON editing.

Claude Desktop. Open Settings → Developer → Edit Config, drop the JSON block above into claude_desktop_config.json, restart the app. The Godot tools show up under the tools menu in a new conversation.

Codex CLI. The flow takes under two minutes — there's a short video walkthrough (MrWonderHow, ~4 months old, 17K+ views) covering it: open Codex settings at 0:18, add the MCP server at 0:27, environment variables at 1:08.

Cursor and VS Code. Both read the same JSON schema in their MCP settings (Cursor: Settings → MCP; VS Code: Copilot agent config). Paste, save, reload. The server is client-agnostic — that's the point of the protocol.

What it can actually do once connected

Three workflows show up again and again in community discussion.

Scene building by description. "Create a player scene with a CharacterBody2D root, add a Sprite2D and a CollisionShape2D." The server creates the scene, adds each node with its properties set, and saves it. Loading sprites into Sprite2D nodes and exporting 3D scenes as MeshLibrary resources for GridMap are covered too (Coding-Solo README).

The fix-run-verify loop. Ask for "make all the walls red." A good server changes the material, launches the game, takes a screenshot, and checks its own work. This end-to-end pattern is what the r/godot thread identified as the real differentiator between servers — and it's the one worth testing with your own project before committing.

Reading errors you'd otherwise copy-paste. Output logs, debugger panel errors, script parse errors — the agent reads them directly and proposes fixes. Less context-switching, fewer transcription mistakes.

One honest caveat: node path handling differs between servers. Some accept /World/Player, World/Player, and ./World/Player interchangeably; others reject two of the three. If your prompts start failing on paths, that's the implementation, not you.

Godot MCP FAQ

Does it work with Godot 4.4 and later? Yes, with a note: resource UID management (reading a file's UID, updating references by resaving) targets Godot 4.4+. On older versions those specific tools don't apply.

Why do directories list 34 servers if only four matter? Low barrier to entry. An MCP server is a small program, so forks and experiments multiply. The four above have maintenance activity and real user discussion behind them; treat the rest as noise until one earns attention.

Is there a Godot MCP in C#? Yes — IvanMurzak/Godot-MCP is a C# editor addon with 42 tools across 12 families, distributed via NuGet and sharing its MCP stack with Unity-MCP.

It connected but the tools do nothing. Now what? Restart the client first (servers register at startup). Then re-add the server with DEBUG=true and check the server-side logs — a missing Godot binary in GODOT_PATH is the most common cause.

The missing piece: 3D assets for your AI-built scenes

The MCP workflow handles code, scenes, and debugging. Nobody in these threads talks about where the actual 3D models come from — and hand-modeling a character or prop takes longer than everything above combined.

That's the gap we work on. Our generator turns a text prompt or a single image into a textured GLB in minutes, and Godot imports GLB natively — drop the file into the project, and it's a usable mesh with materials. If you want to check a model before importing, our free online viewer opens it in the browser. We also wrote guides on downloading models from MakerWorld and comparing AI 3D model generators if you're evaluating options.

Start today

Install Node.js 18+, run the one-line command, restart your client, and ask it to create a scene. Then give it something ugly to fix — that's when you'll know whether this workflow is for you. If you need a 3D asset for the scene it just built, our editor is free to try.

Written by the Trellis2 team. Facts above were verified against linked sources in September 2026; Godot MCP servers evolve quickly, so treat tool counts as snapshots.