Claude Code
AI Code Editors & Agents
Anthropic's agentic coding tool for the terminal, VS Code and JetBrains. Uses a Claude Pro/Max plan or the API.
#cli#agentHome › Godot MCP: Connect Claude Code, Cursor or Codex to the Godot Editor (2026)
An MCP server lets a coding agent like Claude Code, Cursor or Codex do more in Godot than edit text files: run your project and read its errors, build scenes, or drive a live editor. Stock Godot doesn't ship one, so most people pick a community server; Flockbay's desktop app is a separate path with MCP built in (see the Flockbay section below). This guide compares three of the most-used community servers from their own repositories (checked October 31, 2026), shows the setup for each client, and reports what happened when we ran them on our own machine.
Last updated:
Free download · one page + PDF · updated weekly, current edition November 16, 2026
The best AI tool for each job in a solo or indie game (3D, sprites and pixel art, animation, audio, NPCs), MCP setups for Unity, Unreal, Godot and Roblox, and which free plans you can actually ship with.
Yours free when you join the VibeStack Weekly: new AI game-dev tools and releases every Monday, 5-minute read. Unsubscribe anytime.
run_scene call (commercial plugin; works on its free Hobby plan with a sign-in; we haven't installed it).Only want the agent to write GDScript? You don't need MCP at all: open the project folder in Cursor or run Claude Code or OpenAI Codex in it. Our AI tools for Godot guide covers that workflow. MCP is for the step after: letting the agent check its own work in the engine.
Flockbay is a free AI Godot desktop app (Windows, macOS, Linux) that runs its own MCP server for the game you have open. Per Flockbay's MCP docs (checked November 5, 2026), you turn it on under Connectors › Connect your agent (MCP), then register it with Claude Code, Codex, Cursor or another MCP client (on Windows: flockbay mcp). The project is a normal Godot 4.6+ project (bundled Godot 4.7.2), not a fork. This is a different path from the community servers below: you install Flockbay instead of (or alongside) a separate MCP package. Full product and pricing notes: AI tools for Godot: Flockbay. We haven't run Flockbay's MCP hands-on.
Not that we could find. The Godot blog (latest posts: the Godot 4.8 beta snapshots) has no MCP announcement, and the MCP add-ons in Godot's Asset Library are listed as Community submissions. That's different from Unreal, where Epic ships Unreal MCP inside Unreal Engine 5.8 (see our Unreal MCP and UEFN MCP setup guide) from Roblox, which builds an MCP server into Studio (see our Roblox Studio MCP setup guide), and from Unity, whose free CLI includes one (see our Unity MCP setup guide). For Godot, the server is a third-party project you choose and keep up to date yourself. How all four engines compare is in game engine MCP servers compared.
For reference: the current stable Godot is 4.7.2 (August 18, 2026), and 4.8 is in beta.
Want to see a whole project built this way? Tripo's tutorial The Red Scarf (October 21, 2026) makes a third-person boss-fight demo in Godot 4.7.2 with Claude Code and a Godot MCP server (running the game, screenshots, logs, simulated input), plus Tripo's CLI for the 3D assets. The CLI and what it costs are in our Tripo review.
There are more than three on GitHub and in the Asset Library. We picked the most-starred server overall plus the two live-editor add-ons that are updated this autumn and install from inside Godot (AssetLib or the Asset Store), and checked each one's README, licence and release dates. Numbers are as of October 31, 2026.
| Coding-Solo/godot-mcp | Godot AI (hi-godot) | Godlink MCP (tomyud1) | |
|---|---|---|---|
| How it talks to Godot | Runs the Godot executable from the command line (no add-on) | Editor add-on + Python server; client connects through godot-ai attach | Editor add-on + Node server over a local WebSocket |
| Needs | Godot, Node.js 18+ | Godot 4.7+, uv | Godot 4.4+, Node.js |
| Editor must be open? | No (one tool opens it) | Yes | Yes |
| Tools | 14 (our tools/list) | 46 tools, 120+ operations (its docs) | 69 (README); 71 in our tools/list |
| Highlights | Run the project, capture output, create scenes, add nodes, load sprites, UIDs | Live scene edits, signals, UI, materials, animation, screenshots, test_run, signed updates | Live scene edits, run scene, screenshots, send input, its own undo, project visualizer |
| Clients in README | Claude Code, Cursor, Cline, any MCP client | Dock configures 26, incl. Claude Code, Cursor, Codex | Claude Desktop, Cursor, Claude Code, any MCP client |
| Licence | MIT | MIT | MIT |
| GitHub stars | 6,456 | 3,308 | 448 |
| Latest version | Last commit Apr 16, 2026 (a security fix); npm still 0.1.1 from Feb 3, 2026, without it; no GitHub releases | v4.3.1 (Oct 24, 2026) | npm 0.6.1 (Oct 17, 2026) |
Two things stand out. Coding-Solo's server is the most starred but hasn't had a commit since April 2026, and its npm package is older still (see below). Godot AI and Godlink are actively updated, but they need an add-on in your project and a running editor. Godot AI also collects anonymous telemetry by default (installation ID, event, outcome, duration, platform and version, never code or file names, per its README); turn it off with GODOT_AI_DISABLE_TELEMETRY=true or in the editor.
Others we saw but didn't compare: tugcantopaloglu/godot-mcp (MIT, 506 stars, 157 tools per its README, Godot 4.4+, built from source with npm) and ee0pdt/Godot-MCP (MIT, 621 stars, last pushed March 2025). We haven't checked them beyond their GitHub pages.
Godot Editor MCP (repo hybridindie/godot-mcp, PyPI godot-editor-mcp) is a fourth option worth knowing about: a Python MCP server plus an editor add-on that drives the live Godot editor. Its stable 2026.11.04 release went out on November 4, 2026 (MIT, 53 GitHub stars on November 7). It's younger and much less starred than the three above, but it's the only one whose add-on we've connected to a real editor.
core and inspection (29 tools) are on at start; the agent turns on the rest with godot_enable_toolset, so its tool list stays short until it needs scene editing, runtime, tests, export and so on.pip install --pre).validate_project tool that runs headless, run_tests aimed at one GUT test file or folder, and project-defined tools: tag a typed GDScript function with ## @mcp_tool and it shows up as a godot_project_* tool.godot-editor-mcp config --client writes the entry for claude-code, codex, cursor, gemini, opencode or vscode, and godot-editor-mcp doctor checks the setup and suggests a fix for each failure.pip install godot-editor-mcp # or: uv tool install godot-editor-mcp
curl -L -o godot_mcp_addon.zip \
https://github.com/hybridindie/godot-mcp/releases/download/2026.11.04/godot_mcp_addon.zip
unzip godot_mcp_addon.zip -d /path/to/your/project/
godot-editor-mcp doctor --project /path/to/your/projectEnable Godot Editor MCP - Addon under Project → Project Settings → Plugins (it's also on the Godot Asset Store). The add-on connects out to the server on ws://127.0.0.1:9080, so the editor and the server can start in either order. For Claude Code, config --client claude-code --project … printed this for us:
{
"mcpServers": {
"godot-mcp": {
"command": "uvx",
"args": ["godot-editor-mcp"],
"env": { "GODOT_MCP_PROJECT_DIR": "/path/to/your/project" }
}
}
}Add GODOT_MCP_GODOT_BIN (the path to your Godot executable) to that env block. Without it, the run and validate tools fail with “Godot binary not found”, even though editor editing works.
Linux, Godot 4.7.2 editor started headless, server 2026.11.04 talking raw MCP over stdio (the same messages a client sends; we didn't go through Claude Code, Cursor or Codex). Checked November 7, 2026:
godot_health_check reported the bridge connected, matching add-on and server versions, and the editor ready.tools/list returned 29 tools at start, 64 after enabling scene_edit and runtime, and 74 with analysis.create_node with dry_run returned a receipt with status noop. The real call added a CharacterBody2D and returned a receipt listing the added node and reversible_by: undo.delete_node without confirm=true was refused with “destructive and may be irreversible”.save_scene reports reversible_by: none. When we saved and then called godot_undo, the node left the editor but was still in the .tscn on disk (the file only changes if you save again). Commit to git before the agent starts and you won't depend on undo.GODOT_MCP_GODOT_BIN set, run_and_capture on a script that quits returned exit code 0, our printed line, the push_warning as a warning and the push_error as an error with a GDScript backtrace. On a game that never quits it timed out at our 8-second limit and returned no output lines at all, so have test scenes quit, or use the live play tools instead.validate_project returned valid with no findings on our small test project.Not tested: screenshots, input simulation, GUT tests, exports, project-defined tools, HTTP mode, Windows and macOS. Tool page: Godot Editor MCP.
Ziva is a commercial AI agent that lives in a dock inside the Godot editor (Godot 4.2 or later on Windows, macOS and Linux; a proprietary plugin from Zivash Inc., not open source, and not related to Ziva Dynamics). The plugin also starts a local MCP server called ziva-godot, so Claude Code, Cursor, Codex and other MCP clients can use Ziva's editor tools. On November 7, 2026 Ziva documented the step most servers split across several calls: run_scene runs a scene in the open editor, sends timed input while it runs, and returns a screenshot of the final frame plus that run's console output and runtime errors.
at_ms) and a hold time (hold_ms), and the reply includes a delivery report with the frame each press and release landed on, so the agent can tell an input the game never got from one it ignored.get_scene_tree, get_godot_errors (script and runtime errors, stack traces, print() output), get_screenshot (the editor, not the game), run_tests, and start_godot, which lets a command-line client started in your project folder open the editor itself.addons/ziva_agent folder into your project), open the project and sign in to Ziva in its dock. Then open Settings › Models & Providers › Ziva as an MCP server, choose your app and click Install for Claude Code (it runs claude mcp add --scope user ziva-godot -- …, so it's registered for every project) or Install for Cursor (it writes ziva-godot into the project's .cursor/mcp.json). No Node.js or uv needed. Turn on Enable playtest tool under Settings › Agent, or run_scene won't appear.run_scene and get_screenshot need you signed in, because they upload their screenshots to Ziva. Ziva's own agent can run on your existing Claude Code or ChatGPT (Codex) subscription, OpenRouter or a local model on every plan; paid plans are Basic $20, Pro $50 and Ultra $200 a month.Ziva's test, not ours: on November 7 Ziva connected Claude Code 2.1.318 to a Godot 4.7.2 editor running its public Star Catcher sample, which has one planted bug. A four-second run_scene holding ui_right for two seconds took 8.1 seconds and returned the missing %ScoreLabel node error and the null-instance assignment at res://main.gd:15, with a screenshot showing the score stuck at 0. We haven't installed Ziva: these tools need an account sign-in, and our test box runs Godot headless. Ziva also publishes a table of other Godot MCP servers that can run, press and screenshot (Godot MCP Pro, GDAI MCP, Godot AI, Erodenn/godot-mcp-runtime). It discloses that GDAI MCP is made by a Ziva cofounder, so read it as a vendor's comparison.
Free, open-source options for the same loop, per Ziva's table quoting each README (November 7): Godot AI's game_manage sends key, mouse, gamepad and action input and its editor_screenshot can capture the running game (Godot 4.7+), and Erodenn/godot-mcp-runtime (MIT, Node.js 20+, no add-on) injects a temporary bridge for input and screenshots. We haven't tested their input tools either. For checks that run headless in CI, script the input in GUT or GdUnit4 instead (see AI playtesting and QA).
Ziva sources (checked November 9, 2026): the Ziva as an MCP server docs; Ziva's Godot MCP server for Claude Code and Cursor (November 7, 2026) and How to automate playtesting in Godot (updated November 7); the changelog (3.3.6, November 5-7) and GitHub releases (v3.3.6, November 7); plans from ziva.sh and its Terms of Service (last updated November 7, 2026).
We downloaded Godot 4.7.2 for Linux and talked to each server directly over MCP (stdio JSON-RPC, the same messages Claude Code, Cursor or Codex send). Results:
npx -y, then a build from the GitHub source): tools/list returned 14 tools. get_godot_version returned 4.7.2; create_scene and add_node wrote a valid .tscn with a Node2D root and a Sprite2D child (the root is named root, not after the file); run_project started the game, get_debug_output returned the line our script printed, and stop_project stopped it. On our machine Godot fell back to the Compatibility renderer and the Vulkan errors showed up in the output, so expect the agent to see renderer noise next to your own errors.add_node and create_scene only accept plain class names; before it, a node type like res://some_script.gd loaded and instantiated that script, running its _init() in the Godot process. npm's 0.1.1 was published on February 3, before the fix. In our test the npm build accepted res://main.gd as a node type and added it to the scene; the same call on a build from the GitHub source (commit of April 16) returned “Invalid nodeType”. That's why the setup below builds from source.godot-mcp-server 0.6.1): tools/list returned 71 tools before any editor connected. Editor tools then answered "Godot editor is not connected" with a hint to enable the plugin, which is the right failure. We didn't connect the add-on.--exclude-domains to trim tools). We didn't install the add-on or connect a client.We didn't run Claude Code, Cursor or Codex against any of them, and we didn't test on Windows or macOS. Treat the client steps below as each project's and each client's documented setup, not something we've seen work.
You need Godot installed and Node.js 18 or newer. The README's quick start runs the npm package with npx @coding-solo/godot-mcp, but because npm's 0.1.1 predates the April fix (see above), we'd build from source, which the README also documents:
git clone https://github.com/Coding-Solo/godot-mcp.git
cd godot-mcp
npm install
npm run buildThen point your client at build/index.js with an absolute path. The server looks for Godot on its own; if it can't find it, set GODOT_PATH to the Godot executable. DEBUG=true turns on detailed server logs. When a newer version reaches npm, check its date against the fix before switching back to npx.
In the form Claude Code's docs use for stdio servers:
claude mcp add godot \
--env GODOT_PATH=/path/to/godot --transport stdio \
-- node /path/to/godot-mcp/build/index.jsEverything after -- is the server's own command. This adds it to your local scope; add --scope project to write it to .mcp.json for everyone who clones the repo (Claude Code asks each person to approve it the first time). Check it with /mcp or claude mcp get godot.
Put this in .cursor/mcp.json in your project, or ~/.cursor/mcp.json for every project:
{
"mcpServers": {
"godot": {
"command": "node",
"args": ["/path/to/godot-mcp/build/index.js"],
"env": { "GODOT_PATH": "/path/to/godot" }
}
}
}Then turn it on from Customize in the sidebar. Cursor asks before it runs MCP tools by default; click the arrow next to a tool call to see its arguments.
Codex keeps MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project). With the CLI:
codex mcp add godot --env GODOT_PATH=/path/to/godot \
-- node /path/to/godot-mcp/build/index.jsOr by hand:
[mcp_servers.godot]
command = "node"
args = ["/path/to/godot-mcp/build/index.js"]
[mcp_servers.godot.env]
GODOT_PATH = "/path/to/godot"Check with codex mcp list or /mcp in the Codex TUI. If you use an npx command instead (as for Godlink below), the first run downloads the package, and Codex's default startup_timeout_sec is 10 seconds; add startup_timeout_sec = 30 to the table if the tools don't appear.
First prompt to try: “Use the godot tools to get the Godot version and the project info for this folder, then run the project for a few seconds and show me any errors.”
addons/godot_ai/.Don't hand-write the config. The project says to use the dock-generated command because it pins the matching version, ports and tool domains, and a bare http://127.0.0.1:8000/mcp entry can't authenticate. For clients the dock doesn't write, it shows a Run this manually command.
Things to know before you press Configure:
project and press Configure again. Configure removes existing godot-ai entries from every scope, which can change a checked-in .mcp.json.claude run in that project.addons/godot_ai/..cs files but doesn't build .NET or report compiler errors. GDScript is parse-checked and hot-reloaded.addons/godot_mcp/ from the repo.Claude Code (from the README):
claude mcp add godot -- npx -y godot-mcp-serverFor Cursor, the README's JSON is the same shape as above with "args": ["-y", "godot-mcp-server"]; on Windows it uses "command": "cmd" with "args": ["/c", "npx", "-y", "godot-mcp-server"]. For Codex, in Codex's format:
[mcp_servers.godot]
command = "npx"
args = ["-y", "godot-mcp-server"]One catch the README spells out: Ctrl+Z doesn't undo the agent's changes, because the plugin writes to disk rather than the editor's live tree. Ask the agent to use mcp_undo instead, or roll back with git.
Can (depending on the server): run the game and hand the agent the errors and printed output; create scenes and add nodes; read and set node properties; attach scripts and connect signals; take screenshots of the editor or the running game; send input; run GDScript test suites (Godot AI's test_run). That closes the loop agents are bad at without it: they can see that their code crashed.
Can't, or not reliably:
.cs files but doesn't compile them; none of the three READMEs promise .NET builds.session_activate tool to pin calls to one editor..godot/ folder out of the repo. Commit, branch, let the agent work, then read git diff before you keep anything. Scene files are text, so the diff is readable.enabled_tools and disabled_tools lists per server. Cline-style auto-approve lists like the one in Coding-Solo's README skip that check.--allow-host, which you should only do on a network you trust. Godlink says it's localhost-only. Its visualizer runs a local web page on port 6510.project.godot, override.cfg or .godot/. The other two don't document a limit like that, so assume they can write anywhere in the project.npx command runs whatever version is newest on npm when the client starts, which isn't always the newest code (Coding-Solo's npm package misses the April 2026 fix). Pin an npm version or a git commit, and read the changelog before you move.| Symptom | Likely cause | Fix |
|---|---|---|
| “Godot not found” (Coding-Solo) | Godot isn't where the server looks | Set GODOT_PATH to the Godot executable |
| Tools never appear in Codex | First npx download takes longer than the 10-second default | Raise startup_timeout_sec, or run the npx command once in a terminal first |
| Tools vanish after a Godot AI update | The first launch builds its Python environment | Let the dock's Configure finish (“Installing…”), then restart the client |
| Claude Code shows “Pending approval” | Project-scoped .mcp.json not yet approved | Run claude in the project and approve it |
| Godlink shows MCP: No Agent / Disconnected | Client not running, or server not started | Restart the AI client; check Node.js and the saved config |
| Port already in use | Another server (e.g. Unreal MCP on 8000) has the port | Change one server's port and reconfigure the client |
| “Invalid project path” | Path doesn't contain project.godot | Point at the folder that holds project.godot |
export_presets.cfg as in our Godot web export guide.Related: AI tools for Godot · Godot 4 web export · Unreal MCP and UEFN MCP setup · Roblox Studio MCP setup · AI playtesting and QA · Claude Code vs Codex.
Building with agents? Get the VibeStack Weekly digest: new AI game-dev tools and workflows, every Monday.
Sources (checked October 31, 2026): the GitHub repositories and READMEs of Coding-Solo/godot-mcp, hi-godot/godot-ai (plus its tools reference and client configuration doc) and tomyud1/godot-mcp, with stars, licences and dates from GitHub's API and the npm registry; the Godot blog and download archive; Godot's command line tutorial and version control page; and the MCP docs for Claude Code, Cursor and Codex. The test results are from our own run on a Linux machine with Godot 4.7.2. The Codex snippets for the two Node servers are our translation of each README's command into Codex's documented format; neither README shows Codex. Godot Editor MCP (added November 7, 2026): its GitHub repository, README and 2026.11.04 release notes, docs site and PyPI page, tested on our Linux machine with Godot 4.7.2. All of these servers are community projects. VibeStack Weekly isn't affiliated with them, the Godot Foundation, Anthropic, Anysphere or OpenAI, and none of them pays us.
AI Code Editors & Agents
Anthropic's agentic coding tool for the terminal, VS Code and JetBrains. Uses a Claude Pro/Max plan or the API.
#cli#agentAI Code Editors & Agents
AI-first code editor with agent mode, built on VS Code.
#editor#agentAI Code Editors & Agents
OpenAI's coding agent: CLI, IDE extension, web and cloud tasks. Included in ChatGPT plans (Free with limits). Unity ships an official Codex skills plugin (unity@unity-agent-plugin) for Unity 6+. The ModRetro Chromatic plugin (November 2026) builds Game Boy and Game Boy Color games as GB Studio projects, playtests them in a built-in emulator and can flash them to a Chromatic handheld cartridge.
#cli#agentGame Dev Tools
Free, open-source (MIT) MCP server + Godot editor add-on (hybridindie/godot-mcp; PyPI godot-editor-mcp) that lets Claude Code, Cursor, Codex, OpenCode, Gemini or VS Code drive a live Godot editor. Stable 2026.11.04 (released November 4, 2026; Godot 4.4+, validated on 4.7; Python 3.11+): 201 tools in 29 toolsets, but only core + inspection (29 tools) are on by default and the agent enables the rest. New in this release: change receipts, consent tokens for destructive calls, undo checkpoints, headless validate_project, targeted GUT run_tests and project-defined GDScript tools. We ran it on Linux with a headless Godot 4.7.2 editor over raw MCP (not through Claude Code, Cursor or Codex): the add-on connected, node creation returned change receipts, delete was blocked until confirm=true, and run_and_capture returned our script's output, warnings and errors once GODOT_MCP_GODOT_BIN was set. Community project, not an official Godot Foundation server.
#godot#mcp#agent#open-source#freeGame Dev Tools
AI coding agent that lives in a dock inside the Godot editor (Godot 4.2+, Windows, macOS, Linux; proprietary plugin from Zivash Inc., not related to Ziva Dynamics). It edits scenes, nodes, scripts, signals, resources and tilemaps, reads editor errors, runs tests, writes C# in .NET projects and can install Asset Store add-ons. The plugin also runs a local MCP server (ziva-godot) for Claude Code, Cursor, Codex and other clients; its run_scene tool runs a scene in the open editor, sends timed keys, input actions and clicks, and returns a screenshot of the final frame plus that run's console output and errors. Plans: Hobby free (bring your own Claude Code, ChatGPT/Codex, OpenRouter or local model, plus a small hosted allowance), Basic $20/month, Pro $50 (adds the Full Game Playtest Agent), Ultra $200. run_scene works on Hobby but needs a Ziva sign-in. We haven't installed it.
#godot#agent#mcp#playtestingReach builders, vibe coders & indie game devs. Featured listings from $49/mo.
Advertise →Several, per their own docs. Ziva's run_scene does it in one call: it runs a scene in the open editor, sends timed keys, input actions and clicks, and returns the final frame plus the run's errors (commercial plugin; free Hobby plan with a Ziva sign-in). Free open-source options include Godot AI (game_manage input and a running-game screenshot, Godot 4.7+) and Erodenn/godot-mcp-runtime. Ziva's tool needs the editor open and has no headless mode; for CI, script input tests in GUT or GdUnit4.
Stock Godot and the Godot Foundation don't ship one. The community servers in this guide fill that gap. Separately, Flockbay's desktop app includes its own MCP server for the game you have open; that is Flockbay's product, not an official Godot Foundation server.
For running the project and reading its errors with nothing installed in Godot, Coding-Solo/godot-mcp (MIT, the most GitHub stars). For an agent that edits the open editor, an add-on server: Godot AI (Godot 4.7+, uv) or Godlink MCP by tomyud1 (Godot 4.4+, Node.js).
For Coding-Solo's server, build it from the GitHub source and run: claude mcp add godot --transport stdio -- node /path/to/godot-mcp/build/index.js, adding --env GODOT_PATH=/path/to/godot if it can't find Godot. The README's npx command installs npm 0.1.1, which predates an April 2026 security fix. For Godot AI, press Configure next to Claude Code in its editor dock. Check with /mcp.
In Cursor, add the server to .cursor/mcp.json with a command (node or npx) and its arguments in args. In Codex, add an [mcp_servers.godot] table with command and args to ~/.codex/config.toml, or run codex mcp add. Godot AI's dock writes both for you.
Coding-Solo's server doesn't: it runs the Godot executable from the command line, and in our test it created scenes and ran the project without an editor. Godot AI and Godlink are editor add-ons, so the editor has to be open with the plugin enabled.
It runs code on your machine, including your game's scripts, so treat it like any agent with write access. Commit to git first, work on a branch, keep tool approval on, review the diff, and keep the server on localhost.
Rely on git. Godlink's README says Ctrl+Z doesn't reach AI changes because it writes to disk, so you ask the agent to use its mcp_undo tool instead. Coding-Solo's server edits scene files directly, and Godot AI documents editor undo for some operations but not all. Commit before the agent starts and you can always roll back.
Partly. Godot AI writes and outlines .cs files but doesn't build .NET or report compiler errors, and attaching a .cs script needs a .NET-enabled editor. GDScript is the better-supported path in all three servers.
A free, open-source (MIT) Python MCP server plus Godot editor add-on (hybridindie/godot-mcp, PyPI godot-editor-mcp) that lets Claude Code, Cursor, Codex and other MCP clients drive a live Godot 4.4+ editor. Stable 2026.11.04 (November 4, 2026) has 201 tools in 29 toolsets, with only 29 on by default, plus change receipts, a confirm step for destructive calls and a headless project validator. We connected it to a Godot 4.7.2 editor over raw MCP on November 7, 2026; set GODOT_MCP_GODOT_BIN or its run and validate tools can't find Godot.
Flockbay is a different path: a free desktop AI Godot app with its own built-in MCP server for the open game (Claude Code, Codex, Cursor and other MCP clients). Stock Godot still has no official MCP server; if you stay on stock Godot, use a community server from this guide. Details: /best-ai-tools-for-godot/#flockbay.
Free download · one page + PDF · updated weekly, current edition November 16, 2026
The best AI tool for each job in a solo or indie game (3D, sprites and pixel art, animation, audio, NPCs), MCP setups for Unity, Unreal, Godot and Roblox, and which free plans you can actually ship with.
Yours free when you join the VibeStack Weekly: new AI game-dev tools and releases every Monday, 5-minute read. Unsubscribe anytime.