For advice, paste your Godot code into Claude or ChatGPT. For file edits, run Claude Code or Codex CLI, OpenAI’s coding agent, in the folder containing project.godot. For editor access, add a live-editor MCP server  (a bridge between the AI and Godot) or connect your ChatGPT account through Codex in Ziva.

Prices and versions checked September 19, 2026. Ziva.sh publishes this page and makes Ziva.

On Linux with Godot 4.7.2 , we ran Godot without a window, called MCP tools from scripts and tested both clients’ add/list commands. AI sessions, installers, sign-ins, GUI clicks, Claude Desktop and Ziva steps follow documentation; we ran none and measured neither productivity nor game quality.

TL;DR

MCP costs below cover the bridge; AI-account costs are separate.

The Godot Community Poll 2026  (11,195 respondents, multiple answers allowed) asked which tasks AI helps with. Chat help (route 1) drew 42.6%, agentic coding (route 2) 17.9%, and MCP (route 3) 4.9%. The option “I don’t use AI, and I’m against it” drew 33.6%.

1. Claude or ChatGPT in a chat tab

1. Paste scripts and a screenshot of your node tree (the scene’s object hierarchy), as u/Maximum-Touch-9294 suggests . They warn you will need to paste scripts repeatedly.
2. State your Godot version. u/OhEvolve reported drift toward Godot 3 syntax ; see which model knows current Godot.

For editor access, see section 3. ChatGPT web does not read local Codex configuration files . The ChatGPT desktop app, Codex CLI and Codex IDE extension share those local settings.

2. Claude Code or Codex in the project folder

1. Install Claude Code  or Codex CLI . Claude Code needs a paid plan, Console account or supported cloud provider; Codex accepts a ChatGPT Free account.

2. Create AGENTS.md , a project-folder instruction file, with your Godot executable location and script-check commands. Ziva reads AGENTS.md too.

3. Check claude --version: AGENTS.md support starts at 2.1.277 . CLAUDE.md, CLAUDE.local.md or .claude/CLAUDE.md here or above stops automatic AGENTS.md loading. Import it with @AGENTS.md in CLAUDE.md instead. That import also works on older versions, with Bedrock or other cloud providers, or with telemetry disabled.

4. Add these checks to AGENTS.md, replacing res://player.gd with your script. The second runs the main scene, your project’s starting scene. Replace godot with its executable path if needed.

   Only timeout 60, the 60-second limit, is Linux-specific; remove it elsewhere. Godot’s --quit-after 60 counts game-loop iterations, not seconds.

   timeout 60 godot --headless --path . --check-only --script res://player.gd
   timeout 60 godot --headless --path . --quit-after 60

5. Start Claude Code or Codex where project.godot lives; see project workflow tips. TSCN scene files are mostly human-readable text , so these tools can read scene context.

6. Auto Reload Scripts on External Change defaults on from 4.5 . In 4.2 to 4.4.1 it defaults off : enable it under Editor > Editor Settings > Text Editor > Behavior > Files to see agent edits.

A parse check does not exercise gameplay. Our test scene printed a null-access error at res://runtime_error.gd:5 but returned exit code 0, so read the output too. The trailing scene path selects our test scene. We trimmed the banner and backtrace; [exit=0] is the exit code we printed:

$ timeout 60 godot --headless --path . --quit-after 60 res://runtime_error.tscn
SCRIPT ERROR: Invalid access to property or key 'name' on a base object of type 'null instance'.
          at: _ready (res://runtime_error.gd:5)
[exit=0]

Claude Code starts in auto mode on Pro, Max and Team , where another model reviews actions. Use claude --permission-mode manual for prompts before most actions, including edits and commands. To plan, use claude --permission-mode plan. Codex approvals are not covered here.

Summer Engine’s Claude guide , from a competing game-making AI, says Claude Code, Cursor with Claude and the API “cannot press play, watch the running game, and read a live debugger error.” Our command runs a game and reads its errors. Watching gameplay and inspecting the live debugger remain outside this test.

Rabah Shihab ported his 1993 Amiga game to Godot with Claude Code . His account describes Claude Code launching games and reading output.

From Godot 4.4, move companion .uid files too when moving scripts outside Godot. They preserve resource references. Leaving one behind produced “invalid UID” and “referenced non-existent resource” in our test.

3. Godot MCP for Claude and Codex

Coding-Solo, tomyud1 and hi-godot are GitHub owners. Coding-Solo works with Godot closed; live-editor bridges inspect the open editor and run scenes there. Claude Code started all three servers in our test; Codex only saved configuration.

Coding-Solo’s and tomyud1’s READMEs name their Claude server godot; the Codex commands below are ours. Use distinct names: adding godot twice failed in Claude Code and silently overwrote it in Codex.

For Coding-Solo:

1. Install Node.js 18+ and npm. Put Godot on PATH or set GODOT_PATH below.

2. For Claude Code, run:

   claude mcp add godot -- npx @coding-solo/godot-mcp

   Or substitute your executable path:

   claude mcp add godot -e GODOT_PATH=/path/to/godot -e DEBUG=true -- npx @coding-solo/godot-mcp

3. For Codex, run:

   codex mcp add godot -- npx @coding-solo/godot-mcp

   Or substitute your executable path:

   codex mcp add godot --env GODOT_PATH=/path/to/godot --env DEBUG=true -- npx @coding-solo/godot-mcp

A wrong GODOT_PATH silently uses Godot on PATH; DEBUG exposes this.

For tomyud1:

1. Install Node.js and Godot AI Assistant tools MCP, asset 4767 , from AssetLib (Godot’s addon browser). The author is tomyud (tomyud1 on GitHub).

2. Enable Godot MCP under Project > Project Settings > Plugins.

3. For Claude Code, run:

   claude mcp add godot-live -- npx -y godot-mcp-server

   For Codex:

   codex mcp add godot-live -- npx -y godot-mcp-server

4. Restart the client, then choose Project > Reload Current Project. Green MCP: Agent Active confirms connection to Godot; two clients show MCP: Agents (2). The README says “MCP Connected”.

Per tomyud1’s README, ask the agent to undo with mcp_undo; Ctrl+Z cannot undo AI edits. After run_scene, its get_errors tool returned a runtime error with file and line.

For hi-godot:

1. Install uv for uvx, the Python tool runner its README requires.
2. Install Godot AI, asset 5050, by dlight . Choose AssetLib’s 3.2.1 for Godot 4.5+; its connection and client settings passed on 4.7.2. GitHub’s version 4 needs 4.7+.
3. Enable it under Project > Project Settings > Plugins; click Configure beside your client in its dock.

For Ziva, install it, open your project and create an account. MCP setup arrived in 3.0.0. Per its MCP docs:

1. Open the project and wait for Ziva.
2. Open Ziva Settings.
3. Select Integrations > Ziva as an MCP server.
4. Confirm Running and a tool count.
5. Choose your AI application.
6. Select Install for that application.
7. Restart the client to discover ziva-godot.

For manual setup, click Copy beside your application in Integrations; its configuration is specific to your computer.

From the project folder:

claude mcp list
codex mcp list

claude mcp list starts servers added above; ✔ Connected proves startup, not a connection to the open editor. codex mcp list only lists configuration.

Check tomyud1’s green MCP label or Ziva’s Running and tool count. Ask your agent to run hi-godot’s project_run, then logs_read. For Coding-Solo, request get_debug_output seconds after run_project: immediate calls returned nothing; waiting gave errors with file and line.

For Claude Desktop , use hi-godot’s Configure or Ziva’s Install. Otherwise, open Settings > Developer > Edit Config and merge your chosen entry:

{
  "mcpServers": {
    "godot": {
      "command": "npx",
      "args": ["@coding-solo/godot-mcp"]
    },
    "godot-live": {
      "command": "npx",
      "args": ["-y", "godot-mcp-server"]
    }
  }
}

On Windows, replace tomyud1’s entry with:

"godot-live": {
  "command": "cmd",
  "args": ["/c", "npx", "-y", "godot-mcp-server"]
}

Save, quit completely, then restart.

4. Your Claude or ChatGPT account inside Godot

Sign in to Ziva; connect your account:

1. Open Ziva Settings > Models & Providers > Use Existing Subscriptions.
2. Select Connect beside Codex (ChatGPT account) or Claude Code (Anthropic account), then finish browser sign-in.

This connection has worked on Hobby since 3.1.2. Requests use your provider allowance, with its limits.

Since 3.1.2, agents receive Godot errors with file/line; since 3.2.5, tool results include errors caused by their edits.

PurpleJelly’s GodotAI, asset 4916 , is proprietary and separate from hi-godot. Its listing offers Claude, ChatGPT, OpenRouter, Ollama and a built-in proxy for Claude Pro or Max subscriptions. Its dock inserts code at your cursor with active-script and scene-tree context.

Limits to know

Ziva ships closed-source compiled releases . GitHub’s automatic source archives contain the README and support files. Ziva’s terms forbid decompiling. Coding-Solo, hi-godot and tomyud1 are MIT-licensed: you can audit or modify their source.

Ziva needs Godot 4.2 or later. Hobby includes $3/month of AI usage; hosted Sonnet and Opus need Pro at $50/month, as does the Playtest Agent. Ziva has no inline autocomplete.

Ziva does not store prompts, code or project data from AI requests on its servers, and never uses your code to train AI models. Cloud providers process task context under their own retention terms.

Only connect trusted servers: MCP tools can read or change data. The npx command uses Coding-Solo’s only npm release, 0.1.1, published February 3, 2026 . It fixes command injection through projectPath (CVE-2026-25546) in pre-0.1.1 versions, never published to npm.

Review scene and resource edits. u/TripsOverWords warns  that agents can make a mess of these editor-managed files.

Related reading

• Ziva vs Godot MCP: Plugin Agent or Open-Source Bridge: five open-source servers compared.
• Ziva vs Claude Code for Godot: terminal or editor.
• Ziva vs ChatGPT for Game Development in Godot: the chat workflow.
• Claude Godot Code: Why It Beats ChatGPT in 2026: model knowledge and version context.