Ziva as an MCP Server

Use Ziva's Godot tools from Claude Code, Codex, Cursor or another MCP app. The app can inspect scenes, edit nodes and scripts, read errors and run your game through Ziva.

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 applicationCopy Anchor Link

1. Open your project in Godot and wait for Ziva to start.
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.

CursorCopy Anchor Link

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 CodeCopy Anchor Link

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 connectionCopy Anchor Link

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. The available list depends on Ziva's settings, including whether playtesting and image generation are enabled.

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 closedCopy Anchor Link

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.

TroubleshootingCopy Anchor Link

• 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.
• Claude Code installation fails: check that claude runs in your terminal. Copy the displayed command and run it there to see the error.