Godot AI vs Godot-MCP vs Godot MCP Toolkit vs Godlink: Which Bridge Wins in 2026


Four bridges promise to wire Claude or Cursor into your Godot editor, and three of them have almost the same name. The short answer: Godot AI, published by dlight, is the 2026 default for beginners — but only on Godot 4.7 or newer, and mainly for GDScript. Two questions decide the real winner for you: which Godot version you run, and whether you write GDScript or C#. On Godot 4.2 through 4.6, or if you want AI edits that land in the editor’s undo history, Godot MCP Toolkit takes the crown instead.

How the facts were checked: every version number, date, requirement and tool count below was read from the vendors’ own pages — GitHub repositories, the Godot Asset Store and the Godot Asset Library — and verified on 2026-11-03. No vendor paid for, sponsored or previewed this article. This review is based on the vendors’ official documentation and store listings — we did not run any of these tools hands-on.

What an “AI-agent bridge” actually does

A bridge is two pieces: a small server running on your computer and an addon inside the Godot editor, connected over a local socket. Your AI client calls the server, the server calls the addon, and the addon edits your project. Four projects do this four different ways, which is exactly why the names blur together.

The glue is MCP, the Model Context Protocol — an open specification for how an AI client asks a local program to run a named tool with named arguments. Four words recur below and are worth pinning down now. stdio means the client launches the server as a child process and talks to it through standard input and output. A WebSocket is a two-way connection held open over a numbered network port. Loopback means 127.0.0.1: the machine accepts connections only from itself, not from your network. And MONO is the .NET-enabled build of Godot, the one that can compile C# addons.

The four bridges at a glance

All four speak MCP and all four are community projects, so the protocol is not the difference — the version floor, the runtime you must install, and how much of the editor each one exposes are. The table below is the only spec sheet in this review; everything after it is about what those numbers mean in practice.

Bridge Version & date Godot range Runtime prerequisite License Tool surface Momentum
Godot AI (hi-godot, publisher dlight) 4.3.1 · 2026-10-25 4.7+ uv (runs a Python server) + an MCP client MIT 46 tools, 120+ operations 21,000+ monthly active installs; 30M+ tool calls in three months; 3,200+ GitHub stars
Godot-MCP (IvanMurzak) 0.34.0 · 2026-10-31 4.3+, C#/.NET (mono) edition .NET 8 SDK + six NuGet references in your .csproj Apache-2.0 24 tools across 9 families —
Godot MCP Toolkit (NPGameDev) 1.1.2 · 2026-10-29 4.2–4.7, desktop Node.js 22+ — 113 tools, 150+ operations 21 store reviews, all recommended
Godlink (tomyud1/godot-mcp) no version number in the listing we read 4.4+ Node.js bridge, WebSocket port 6505 MIT 69 tools across 7 categories 449 GitHub stars, 52 forks, 38 commits

Now the disambiguation, because this is where beginners lose an evening. Godot AI is the batteries-included one-click bridge. Godot-MCP is the C#-first, cloud-connected one, the Godot sibling of Unity-MCP. Godot MCP Toolkit is the undo-safe, no-telemetry one with the widest version support. And Godlink is the plugin whose GitHub repository is literally named tomyud1/godot-mcp — on the store it is listed as “Godlink MCP”, and on Godot 4.6 and older it shows up in the AssetLib tab as “Godot AI Assistant tools MCP”. Same plugin, three names. Also note there are two Godot AI listings: the store’s current v4, and Asset Library entry 5050, which is version 3.2.5 and the final release for Godot 4.5 and 4.6.

Day one: what setup actually feels like

Godot AI is the only one of the four that sets most clients up for you with one click. The other three ask for a runtime first: Node.js 22+ for the Toolkit, the .NET 8 SDK plus a mono edition of Godot for Godot-MCP, and a Node bridge for Godlink.

Godot AI needs three things: Godot 4.7+, uv, and an MCP client. uv is a single installer that fetches and runs Python programs for you — you are not writing Python, you are installing one binary so the bridge’s Python server has somewhere to live. From there it configures 26 MCP clients in one click, including Claude Code, Claude Desktop, Codex, Cursor, VS Code, Antigravity, Gemini CLI and Hermes Agent, and prints a “Run this manually” command for anything else. Two documentation gaps are already visible in the store reviews: a missing Windows PowerShell policy step, and a plugin that cannot update itself on immutable Linux distributions.

Godot MCP Toolkit is the classic addon dance — install, enable under Project Settings → Plugins, run the setup wizard, and let it write your project’s .mcp.json. The prerequisite is Node.js 22+ on your machine, because the companion bridge @npgamedev/godot-mcp-server is fetched by npx on first connect rather than installed globally. That is one installer, then one wizard.

Godot-MCP is the heaviest lift of the four and the dossier is blunt about why. It requires the C#/.NET (mono) edition of Godot 4.3+ — the standard GDScript-only build cannot compile the addon — plus the .NET 8 SDK. Then, because Godot compiles every .cs file in a project into a single assembly, your .csproj has to declare six NuGet package references (com.IvanMurzak.ReflectorNet 5.5.1, com.IvanMurzak.McpPlugin 8.14.0, com.IvanMurzak.Rql 0.3.0, com.IvanMurzak.CodeExec 0.4.0, com.IvanMurzak.CodeExec.Roslyn 0.4.0 and Microsoft.CodeAnalysis.CSharp 4.12.0) before a dotnet restore. No manual DLL copying — the assembly resolver finds them in the NuGet global-packages folder — but it is a .NET developer’s setup, not a beginner’s.

Godlink sits in the middle: a Node.js MCP server over stdio, an editor plugin reached over WebSocket on port 6505, and the visualizer on 6510.

Which one can’t wreck your project

Godot MCP Toolkit and Godot AI publish the most detailed safety stories: the Toolkit routes edits through the editor’s own undo history and collects no telemetry, while Godot AI ships signed releases and confines writes to the project folder. Godlink is honest about its gap — Ctrl+Z does not reach AI changes.

Godot MCP Toolkit wins on reversibility. Scene and node edits go through the editor’s undo history, so an AI change reverts exactly like one of yours. Its editor server binds 127.0.0.1 only, every client must present a per-project session token as its first message, filesystem tools are boundary-checked to res:// and user:// with path traversal and absolute OS paths rejected, and an optional read-only mode (GODOT_MCP_READ_ONLY=1) hides every mutating tool. Neither the plugin nor the bridge collects or uploads anything; the update check runs at most once a day per project and sends nothing about the project. Exports strip the plugin’s scripts and the project’s .mcp.json from shipped builds.

Godot AI takes the opposite approach: harden the delivery. Releases are signed and verified file by file before install, writes are confined to the project with project.godot, override.cfg and .godot/ off-limits, dependencies are pinned and security advisories are published. Version 4.3.1 is itself a security release: it removes emSign (eMudhra) root certificates compromised in October 2026, updates FastMCP to 4.1.3 to fix GHSA-7xgj-8392-5q4r and GHSA-vqqp-x5qm-5qp4, and closes a Windows path-spelling bypass of write protection (GHSA-57gf-8755-xc98). Architecturally, both local hops use independent rotating capabilities and the editor WebSocket stays loopback-only. Telemetry is anonymous — install UUID, event, outcome, duration, platform and version, never code, scene contents, project or file names — and GODOT_AI_DISABLE_TELEMETRY=true turns it off.

Godlink states its own limitation plainly: the plugin writes to disk rather than to the live editor tree, so Ctrl+Z will not reach an AI change. Its Undo & Batching group is the intended remedy — mcp_undo reverses any AI change, and many changes can run as one all-or-nothing batch. It is local only, with no remote connections.

Godot-MCP connects through the hosted cloud backend at ai-game.dev by default, or your own self-hosted server. If a third party in the path is a dealbreaker, that is the line to read twice.

Day-two powers: debugging, playtesting, and the C# question

After setup, the Toolkit has the deepest debugging and GDScript language tooling, Godot-MCP gives the agent RQL as a single query language for scenes and editor state, Godlink adds a browser visualizer on port 6510, and Godot AI leans on screenshots and play-testing so the model can see what it built.

Godot MCP Toolkit carries 113 tools over 150+ operations, but only a 36-tool core loads at connect; the rest sit in 28 on-demand groups the agent activates through discover_tools, keeping the list inside each client’s budget. It debugs with breakpoints, stepping, debug state and crash diagnostics from a captured error buffer, runs playtests that start and stop the game, read live node state, capture screenshots, simulate input including typed text, and read logs, and backs GDScript with the project’s own language server — diagnostics, document symbols, go to definition, find references, hover, completion and a project-wide error scan. Custom tools are written in GDScript through an extension API, hot-reload, and appear to the agent exactly like built-ins. Multiple editors and agents are supported: each project keeps its own session token and state, each editor publishes itself to a machine-wide registry, and while mutations queue and run one at a time in arrival order, reads run alongside.

Godot-MCP drives the editor through RQL — a query language for scene nodes, resources, scenes and editor state, split into rql-query, rql-mutate and rql-schema. Its 24 tools span nine families including reflection and runtime-errors. This is the one to pick if your project is already C#: the MCP and reflection stack is shared with Unity-MCP and consumed from nuget.org as package references rather than forked.

Godlink is the only one with a visualizer. map_project opens a browser explorer at localhost:6510 with a force-directed graph of scripts and their relationships; click a script to see variables, functions, signals and connections, edit code there and watch changes sync to Godot in real time, use the scene view to edit node properties, and find usages before refactoring. It also generates 2D sprites from SVG. Its own documentation warns the AI cannot build 100% of a game alone — complex UI layouts and scene compositing are named weak spots.

Godot AI supports GDScript fully: scripts are parse-validated, hot-reloaded, attached and outlined. C# is text-only. script_create and script_patch write .cs files and script_manage(op="find_symbols") outlines them, but it does not build .NET or report compiler errors — and attaching a .cs needs a .NET-enabled editor build anyway. In practice that means Godot AI can write C# it cannot check.

The one-minute decision table

Find your situation in the left column and take the named tool; if two rows apply, the more specific one wins. The Godot-version row matters most, because a frozen Godot AI listing still exists for older engine releases.

If this is you Pick Because
On Godot 4.2, 4.3, 4.4, 4.5 or 4.6 Godot MCP Toolkit It spans 4.2–4.7; every other bridge has a higher floor
On Godot 4.7+, writing GDScript Godot AI Its 4.7 floor matches yours and most clients configure in one click
On 4.5/4.6 and tempted by Godot AI Upgrade to 4.7 first — or take the Toolkit The 3.2.5 Asset Library listing is final for 4.5/4.6 and gets no further updates or security fixes
A C#/.NET shop Godot-MCP Godot AI writes .cs as text only — no .NET build, no compiler errors
Want nothing leaving the machine Godot MCP Toolkit No telemetry at all and a loopback-only server; fetch the bridge once, then it is local
Want to see what the agent did Godlink Browser visualizer on localhost:6510 with script graph, live code sync and find-usages
Want AI edits you can undo Godot MCP Toolkit Edits go through the editor’s own undo history

Who should pick which

Four reader profiles, four named picks, no hedging. If you do not recognise yourself below, use the decision table above — these are the same tools, matched to how you actually work rather than to a feature count.

The first-game beginner on Godot 4.7 writing GDScript → Godot AI. It is the shortest path from a fresh Godot download to “the AI built me a UI and took a screenshot of it”, and 4.3.1 shows the project is patching security issues quickly.

The C# developer porting Unity habits → Godot-MCP. The MONO editor, the .NET 8 SDK and six NuGet references are the price of a bridge that actually understands a C# project, and the Unity-MCP lineage means the reflection layer is not a first attempt.

The teacher, team lead or anyone who reviews every change → Godot MCP Toolkit. Undo-history edits, loopback-only networking, a read-only switch and zero telemetry are the four things you need before letting a model near someone else’s project.

The visual tinkerer with an existing project → Godlink. The :6510 explorer is the only feature in this whole comparison that shows you the shape of your codebase rather than describing it, and mcp_undo covers the Ctrl+Z gap.

FAQ

Five questions beginners actually ask, answered from the vendors’ documentation: runtime knowledge, running more than one bridge, the older Godot AI listing, whether project code leaves your machine, and undoing what the agent did. Each answer comes from the same 2026-11-03 snapshot used above.

Do I need to know Python or Node.js?

Install, not author. Godot AI needs uv so its Python server can run, but you never write Python. Godot MCP Toolkit needs Node.js 22+ because its bridge is fetched by npx on first connect. Godlink runs a Node.js bridge too, and Godot-MCP swaps all of that for the .NET 8 SDK.

Can I run two bridges at once?

Don’t — pick one. Godlink allows multiple AI clients but only one Godot editor at a time, and stacking two plugins that both mutate the same scene is how you get confusing diffs. If you need two workflows, run them in separate projects rather than in the same editor.

I’m on Godot 4.5 — is the old Godot AI safe?

It is frozen, not patched. Asset Library entry 5050 is version 3.2.5, the final release for Godot 4.5 and 4.6, and it gets no further updates or security fixes; v4 requires Godot 4.7+. On 4.5 the safer plan is Godot MCP Toolkit, which lists support from 4.2 through 4.7.

Does my project code leave my machine?

It depends entirely on the bridge. Godot AI’s telemetry is anonymous — UUID, event, outcome, duration, platform, version — never code, scene contents, project or file names, and one environment variable disables it. Godot MCP Toolkit collects nothing and binds to 127.0.0.1. Godlink is local only. Godot-MCP connects through ai-game.dev by default, with a self-hosted server as the alternative.

Can I undo what the AI did?

Two of the four make this explicit. Godot MCP Toolkit routes edits through the editor’s undo history, so Ctrl+Z works as usual. Godlink writes to disk instead, so Ctrl+Z misses AI changes and you use the mcp_undo tool or its all-or-nothing batches. For the other two, verify the behaviour in the current docs before you let an agent loose on a project you care about.