Ziva.sh

Agen AI editor Godot eksklusif dengan server MCP lokal yang memungkinkan Cursor dan Claude Code memeriksa pohon adegan, membaca error Godot, mengambil tangkapan layar editor, dan menjalankan adegan.

Dokumentasi

Godot MCP Server for Claude Code, Codex and Cursor [#godot-mcp-server-for-claude-code-codex-and-cursor]

Ziva is a Godot MCP server for Claude Code: one click in Ziva's dock registers ziva-godot with claude mcp add, and Claude Code can then run your game, send input, take screenshots and read Godot's errors. Cursor, Codex and other MCP apps get the same tools. Ziva's run_scene tool presses keys, clicks and uses input actions while your game runs, then returns a screenshot and the errors in one call. The app can also read Godot's errors with get_godot_errors, inspect scenes and edit nodes and scripts through Ziva. To compare Ziva with other Godot MCP servers, see best Godot MCP server for Claude Code and Cursor (tested).

Ziva runs locally on your computer, not at a hosted MCP URL. Install your AI app on the same computer and install Ziva in your Godot project first. Ziva supports Godot 4.2 or later on Windows, macOS and Linux.

Connect an AI application [#connect-an-ai-application]

  1. Open your project in Godot, wait for Ziva to start and sign in to Ziva in its dock.
  2. In Ziva, open Settings β†’ Models & Providers β†’ Ziva as an MCP server and check that it shows Running.
  3. Under AI application, choose your app and follow the steps below.

Cursor [#cursor]

  1. Choose Cursor and click Install for Cursor. This adds ziva-godot under mcpServers in your Godot project's .cursor/mcp.json.
  2. Open that same project folder in Cursor and restart Cursor.
  3. Ask: "Use ziva-godot's get_screenshot tool to show the Godot editor."

To configure it yourself, click Copy beneath Or configure it manually and merge the displayed JSON into .cursor/mcp.json. Use the generated command and args, which contain the paths for your computer.

Claude Code [#claude-code]

  1. Make sure the claude command is installed and available on your PATH.
  2. Choose Claude Code and click Install for Claude Code. This runs claude mcp add --scope user ziva-godot -- ... with Ziva's generated command and arguments. The registration is user-wide, not limited to this project.
  3. Start a new Claude Code session from your Godot project folder.
  4. Ask: "Use ziva-godot's get_godot_errors tool to check this project for errors."

To run the registration yourself, click Copy beneath Or configure it manually and run the complete displayed command in your terminal.

Tools and connection [#tools-and-connection]

Both setups use a local stdio bridge, which connects to Ziva's local Streamable HTTP endpoint. You do not need to choose a port or write binary paths yourself.

Tools include get_scene_tree for scene inspection, get_godot_errors for errors, get_screenshot for the editor's appearance, and run_scene to run a scene. run_scene can send keys, input actions, mouse clicks, clicks on buttons and mouse movement while the game runs, then returns a screenshot of the running game plus its console output and runtime errors, so Claude Code or Cursor can playtest a change (how to automate playtesting in Godot). The available list depends on Ziva's settings, including whether playtesting and image generation are enabled.

To see some of these tools in a real run, watch an unedited recording of Ziva's chat using get_scene_tree, run_scene and file-editing tools to fix a runtime error and playtest the fix in a sample Godot project. The project's README lists the exact prompt and every change. An MCP app can call the same tools.

For another listed app, choose it and click Install for [app], then restart it. For an app that isn't listed, choose Other / Raw URL and add the displayed local URL as a Streamable HTTP MCP server in that app. Godot must be open for this direct URL connection.

Only connect an app you trust: these tools can change your project and run its code. MCP calls do not wait for approval in Ziva's dock; use your external app's permission controls.

Work with Godot closed [#work-with-godot-closed]

After setup, command-line apps started from your project folder can call start_godot to open the editor, then use the full tool list. Start from a folder containing project.godot, or a folder beneath it, so Ziva knows which project to open.

Troubleshooting [#troubleshooting]

  • The app doesn't show ziva-godot: restart the app, or click Copy in Ziva and add the configuration to the app's MCP settings yourself.
  • Only start_godot is available: open the project in Godot, then start a new session in the app.
  • "Ziva server not ready": wait for Ziva to start, then reopen Models & Providers.
  • run_scene or get_screenshot says "Not signed in": sign in to Ziva in the Godot dock. These two tools upload their screenshots to Ziva, so they need a Ziva account; the free Hobby plan works.
  • Claude Code installation fails: check that claude runs in your terminal. Copy the displayed command and run it there to see the error.