GODOT AI
Godot AI: The Best AI Assistant for Godot
Ziva is an AI agent that works inside the Godot editor — inspecting scenes and nodes, editing scripts, building UI, and running your tests. It does live scene editing, deep debugging conversations, and agentic, multi-step refactors across your whole project.
Shipped with Ziva
Real Godot games, built with this AI
Not demos — playable games on Steam, GitHub, and itch.io. Click any one to see the source.
One Ziva session: get_godot_errors surfaces the null crop crash in farm_manager.gd, read pulls the script, and edit_file rewrites water_selected_crop to fix it — every tool call shown as a chip in the chat.
The tool surface
163 tools, built for Godot
Every tool Ziva's agent can call inside the editor — 163 of them, grouped into the families below.
Scene & Nodes (4)
Code & Files (10)
Inspection (6)
Tilemaps (6)
Art generation (4)
Testing & Debugging (6)
Project & Docs (5)
Any model. Your keys. One editor.
New frontier models, wired up within 48 hours2
When Anthropic, OpenAI, or Google ship a new flagship, you don't wait for a release cycle. We target same-week support so the smartest model for your task is always one dropdown away.
Bring your own Claude Code or Codex
Already paying for a Claude or OpenAI plan? Point Ziva at your own subscription and run the agent on credits you already have — no double billing, your keys, your account.
Tired of typing? Talk to Godot instead
Ziva ships free voice-to-text right in the editor. Tap the mic, say what you want built or fixed out loud, and the agent runs with it — no typing, no per-minute transcription bill. Drive the whole assistant with your voice while your hands stay on the game.
An MCP server for the whole Godot editor
Under the hood, Ziva exposes the editor as a Model Context Protocol surface — the same tools that drive the in-editor agent are structured, typed operations any MCP-aware client can call. Point Claude Code at the MCP server and it navigates a massive Godot codebase with grep_code, glob, and read, then edits the live project in place.
In the editor
It lives where you build.
Reads and edits the live scene
Ziva inspects the open scene and its nodes with get_scene_tree, then adds, moves, and duplicates nodes and wires up resources directly. It edits the live scene the editor is showing — not a text munge of a .tscn file.
Writes GDScript, C#, and UI
create_file, edit_file, and execute_script run with full project context. The agent writes scripts, builds UI nodes, and runs setup code inside the editor instead of handing you a snippet to paste.
Context-aware chat with file references
Point Ziva at a script or scene and it reads exactly what you reference. It pulls the right files with read, searches the project with grep_code, and finds them by pattern with glob — so the chat answers from your code, not a guess.
Debugging conversations and agentic refactors
get_godot_errors feeds live editor errors straight into the conversation, so you debug against what Godot actually reports. From there Ziva runs multi-step refactors across the project in one chat.
Runs and tests your game
It doesn't just write code. It runs it.
Ziva writes and runs your unit tests, reads editor errors live, and playtests your game — launching it, playing through it, and screenshotting what it sees to analyze.
Writes and runs unit tests
Ziva generates unit tests for your scripts and runs them with run_tests, so a change is verified, not assumed.
run_testsPlaytests your game
Ziva launches your game, plays through it, screenshots what it sees to analyze, and reads the errors it hits — real playtesting, not a dry read.
get_screenshotReads editor errors live
get_godot_errors surfaces what Godot logged, so a runtime failure becomes the agent's next fix instead of your bug report.
get_godot_errorsMultiplayer, included
Multiplayer without standing up a server.
Flip one toggle and Ziva relays your multiplayer game through its own server. No host to provision, no relay to deploy — your peers connect through Ziva's relay and you keep building the game.
Godot AI, answered
What is the best AI for Godot?
Does Godot have an AI assistant?
Can AI build a full Godot game?
Methodology & notes
- 1.We count 163 tools as the distinct operations Ziva's agent can call — the sum of typed parameters across Ziva's 41 MCP tool endpoints, grouped into families on this page. Both numbers mirror Ziva's tool surface as it ships today.
- 2.“Within 48h” is our target for wiring up newly released frontier models from Anthropic, OpenAI, and Google once their APIs are publicly available; actual availability depends on the provider.