“Godot MCP” most often means Coding-Solo/godot-mcp , an MIT-licensed server with 5.7k GitHub stars and 14 tools for launching the editor, running a project and capturing debug output, plus the family of open-source servers around it. Ziva is a Godot plugin with its own agent in the editor dock, and it also runs a local MCP server of its own. This post compares the two shapes and is honest about where the free bridges win.

TL;DR

What Godot MCP is

A Godot MCP server exposes editor or project operations as Model Context Protocol tools. You attach it to a client (Claude Code, Claude Desktop, Cursor, Codex and others), and the client’s model decides when to call the tools. The server has no model and no chat of its own. The main open-source options, with GitHub figures as of September 18, 2026:

Coding-Solo’s tools are launch_editor, run_project, get_debug_output, stop_project, get_godot_version, list_projects, get_project_info, create_scene, add_node, load_sprite, export_mesh_library, save_scene, get_uid and update_project_uids. hi-godot covers scenes, nodes, scripts, signals, UI, materials, animation, particles, cameras and environments through 46 tools and 120+ operations.

Two paid servers share the name but not the licence. GDAI MCP  is a $19 one-time purchase distributed in binary form only . Godot MCP Pro  is proprietary at $15 one-time, with somewhere between 162 and 175 tools depending on which of its own listings you read: the GitHub description says 162, the README says 175, and the Asset Library  says 163. Our May comparisons with GDAI MCP and Godot MCP Pro are superseded by the figures here: the GDAI post described it as open source, which its licence page does not support, and the Godot MCP Pro post quoted $5 where the Asset Library now lists $15.

What Ziva is

Ziva installs like any other Godot plugin for Godot 4.2 and later on Windows, macOS and Linux. The agent in its dock understands scenes, nodes, scripts, resources, project settings, editor errors and the running game (docs). It writes GDScript and C#, searches the Godot docs, runs tests, launches a scene and sends input, generates sprites, and every turn can be undone. Models are hosted from Anthropic, OpenAI, Google and other labs (Godot LLM page), or you connect a Claude Code or Codex account, bring OpenRouter credit (3.2.5), or run Ollama or LM Studio locally. Pricing: Hobby is free with $3/mo of included usage and 50 Ziva Baby messages a day; Basic $20/mo; Pro $50/mo adds the Genius lane, Sonnet and Opus, and the Playtest Agent; Ultra $200/mo.

Feature comparison

The comparison is Ziva’s agent against Coding-Solo/godot-mcp plus a client of your choice.

Where Godot MCP wins

Free and MIT. No account, no plan, no usage meter on the server side. You read the code, fork it, and add the tool you are missing. Ziva’s plugin ships as compiled releases on GitHub  with no published source or licence file, and the terms prohibit decompiling it.

Your client, your model. If you already run Claude Code, Cursor or Claude Desktop, the bridge slots into the tool you have. Nothing new to learn beyond the tool names.

Breadth when you want it. hi-godot’s 46 tools and 120+ operations, or tugcantopaloglu’s 157 tools, give a client-driven agent a large surface. Pick the server that matches the job.

Auditable data path. The server talks to your local editor; what leaves the machine is decided by the client and model you chose, and you can read every line of the server to confirm it.

Where Ziva wins

The agent is included. A bridge gives a model tools; it does not give it a loop tuned for Godot. Ziva’s agent reads the scene tree, reads Godot errors with file and line, sees GDScript errors caused by its own edits (3.2.5), runs tests and playtests, and undoes a bad turn, without you wiring any of it.

Input, not just output. Coding-Solo’s server runs the project and captures debug output; it lists no tool for sending input. Ziva sends keyboard and mouse input to a running scene (3.0.0) and the Playtest Agent plays whole games to a verdict.

Assets. generate_image with RetroDiffusion and ChatGPT backends (3.2.1) plus 3D model placement into the scene. No open-source server in the table lists an AI image generation tool.

A free lane with no client bill. Hobby is $0 with 50 Ziva Baby messages a day (pricing). A bridge is free. The client and model behind it are priced separately.

It is also a Godot MCP server. Ziva as an MCP server exposes scene tree and project inspection, node, scene, script and resource creation, error reading, and run and stop to Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Windsurf, Zed, Cline and other clients, with one-click setup from Ziva Settings. If Godot is closed, clients see a start_godot tool that opens the editor for the project folder. It runs on your machine only; there is no hosted endpoint.

When to pick each

Pick Godot MCP when:

• You want MIT code you can read and fork
• You already have a client and a model subscription
• The job is launch, run, read output, add a node

Pick Ziva when:

• You want an agent that ships with the Godot loop, playtesting and assets
• You want per-turn Undo and errors fed back automatically
• You want a free lane without paying a client on the side

Use both when:

• You keep Claude Code or Cursor for general work and point it at ziva-godot for the editor

Related reading

• Ziva vs Claude Code for Godot: the most common client for these servers
• Ziva vs Cursor for Godot: the same question for Cursor
• Ziva AI Godot Plugin Review: vs godot-ai: our May look at hi-godot’s server
• Is there an AI agent that can playtest a Godot game?: the input side in depth