Godot MCP server for Claude Code and Cursor: run the game, send input, take screenshots

Ziva.sh published a comparison of Godot MCP servers that let Claude Code and Cursor run a Godot game, send it input and capture screenshots, with facts about rival servers quoted from each vendor's page or README as of 7 November 2026. Ziva's own server combines all three functions in one `run_scene` tool that runs a scene in the open Godot editor, sends timed keyboard, mouse, input-action and UI-click input, and returns a screenshot with console output and runtime errors; the plugin supports Godot 4.2 or later and its MCP tools need no paid plan, though `run_scene` and `get_screenshot` require a signed-in Ziva dock (the free Hobby plan works). The comparison also covers Coding-Solo/godot-mcp (free, MIT), GDAI MCP ($19 one-time, binary only), Godot MCP Pro ($15 one-time, proprietary server, Godot 4.4 or later) and Godot AI (free, MIT, Godot 4.7+), and discloses that GDAI MCP is made by Delano Lourenco, a Ziva cofounder.

Godot MCP server for Claude Code and Cursor: run the game, send input, take screenshots Several Godot MCP servers let Claude Code or Cursor run your game, send it input and screenshot the running game: Ziva, Godot MCP Pro, GDAI MCP, Godot AI hi-godot/godot-ai and Erodenn/godot-mcp-runtime, plus Summer Engine's MCP for Summer's own editor. In Ziva https://ziva.sh/docs/ziva-mcp-server , one tool does all three: run scene runs a scene in the open Godot editor, sends timed keyboard, mouse, input-action and UI-click input, and returns a screenshot of the running game with that run's console output and runtime errors. Ziva's get godot errors reads Godot's errors and output, and Ziva's get screenshot captures the editor, not the game. To connect Claude Code, click Install for Claude Code in Ziva's settings, which runs claude mcp add --scope user ziva-godot -- ... for you. The Ziva plugin supports Godot 4.2 or later and its MCP tools need no paid plan, but Ziva's run scene and get screenshot need the Ziva dock signed in the free Hobby plan works . Ziva.sh makes Ziva and publishes this page. Facts about other servers are quoted from each vendor's own page or README as of 7 November 2026, except Godot AI's C statement, from its README on 4 November 2026. Disclosure: GDAI MCP is made by Delano Lourenco, a Ziva cofounder. Godot MCP servers compared: run, input, screenshot godot-mcp-servers-compared-run-input-screenshot | Server | Cost/licence | Setup | Run game | Input to running game | Game screenshot | Errors/output | Godot version | |---|---|---|---|---|---|---|---| | Ziva https://ziva.sh/docs/ziva-mcp-server local MCP server inside the Ziva plugin | Ziva: free Hobby plan works; sign-in needed for screenshots | Ziva: install the plugin, click Install for Claude Code or Install for Cursor ; no Node.js or uv | Ziva: run scene , in the open editor | Ziva: run scene actions, keys, left and right clicks, clicks on a Control by path or text, mouse motion | Ziva: run scene returns the final frame; get screenshot is the editor only | Ziva: run scene output and runtime errors; get godot errors | Ziva: plugin 4.2+; we ran run scene on 4.7.2 | | Coding-Solo/godot-mcp https://github.com/Coding-Solo/godot-mcp | Coding-Solo/godot-mcp: free, MIT | Coding-Solo/godot-mcp: claude mcp add godot -- npx @coding-solo/godot-mcp ; Node.js 18+ | Coding-Solo/godot-mcp: "Execute Godot projects in debug mode" | Coding-Solo/godot-mcp: not stated | Coding-Solo/godot-mcp: not stated | Coding-Solo/godot-mcp: "Retrieve console output and error messages" | Coding-Solo/godot-mcp: not stated; UID tools need 4.4+ | | GDAI MCP https://gdaimcp.com/ | GDAI MCP: "$19 one-time payment", binary only https://gdaimcp.com/license | GDAI MCP: addon in res://addons/ , plus uv | GDAI MCP: play scene | GDAI MCP: simulate input , "keyboard keys and input actions"; mouse not stated | GDAI MCP: get running scene screenshot | GDAI MCP: get godot errors | GDAI MCP: "Godot 4.2+" on its site; its GitHub README says 4.1+ | | Godot MCP Pro https://godot-mcp.abyo.net/ | Godot MCP Pro: "$15 one-time purchase"; server proprietary | Godot MCP Pro: addon plus the Node.js server from the paid package; Node.js 18+ | Godot MCP Pro: play scene | Godot MCP Pro: simulate key , simulate mouse click , simulate mouse move , simulate action , simulate sequence | Godot MCP Pro: get game screenshot | Godot MCP Pro: get editor errors , get output log | Godot MCP Pro: "Godot 4.4 or later" | | Godot AI hi-godot/godot-ai https://github.com/hi-godot/godot-ai | Godot AI: free, MIT | Godot AI: addon from AssetLib, uv , then Configure in the Godot AI dock | Godot AI: project run | Godot AI: game manage with input key , input mouse , input gamepad , input action | Godot AI: editor screenshot of the "running game framebuffer" | Godot AI: logs read | Godot AI: "Godot 4.7+" | | Erodenn/godot-mcp-runtime https://github.com/Erodenn/godot-mcp-runtime | godot-mcp-runtime: free, MIT | godot-mcp-runtime: npx -y godot-mcp-runtime with GODOT PATH ; Node.js 20+; "No Godot addon" | godot-mcp-runtime: run project | godot-mcp-runtime: simulate input : keys, mouse clicks and motion, clicks on UI elements, actions, text | godot-mcp-runtime: take screenshot | godot-mcp-runtime: get debug output | godot-mcp-runtime: "Godot 4.x" | | Summer Engine MCP https://www.summerengine.com/godot-mcp | Summer Engine: "free, MIT-licensed"; "Cloud generation ... uses credits" | Summer Engine: npx -y summer-engine@latest setup claude-code --yes , plus the Summer Engine desktop app | Summer Engine: summer play | Summer Engine: summer game input | Summer Engine: summer screenshot | Summer Engine: summer get debugger errors , summer get console | Summer Engine: its own desktop app, "compatible with Godot 4"; not stock Godot | Notes on the table: - Erodenn/godot-mcp-runtime's README calls it "a lightweight MCP https://modelcontextprotocol.io/ server" whose "runtime bridge adds screenshots, input simulation, UI discovery, and live GDScript against the running scene tree". Erodenn/godot-mcp-runtime injects that bridge as an autoload when run project is called and says it leaves "No leftover autoloads, no modified project files". - Summer Engine's FAQ answers "Does Summer MCP work with the stock Godot editor?" with "No. Its engine tools drive the Summer Engine desktop app, which is compatible with Godot 4 and opens compatible Godot 4 projects." - Godot MCP Pro's site lists "187 Tools, 26 Categories". Godot AI's README lists "46 tools and 120+ operations". - Coding-Solo/godot-mcp had 6,547 GitHub stars on 7 November 2026. Coding-Solo/godot-mcp's README lists running the project, capturing debug output and editing scenes, and lists no input or screenshot tool. Set up Ziva's MCP server in Claude Code or Cursor set-up-zivas-mcp-server-in-claude-code-or-cursor Ziva's MCP server ships inside the Ziva plugin and runs only on your computer, with no hosted URL. Install Ziva https://ziva.sh/docs/installation in your Godot project, open the project in Godot, wait for Ziva to start and sign in to Ziva in its dock. In Ziva, open Settings → Models & Providers → Ziva as an MCP server and check that it shows Running . Claude Code claude-code 1. Make sure the claude command works in your terminal. 2. Under AI application , choose Claude Code and click Install for Claude Code . Ziva runs claude mcp add --scope user ziva-godot -- ... with its generated command, so ziva-godot is available in every project. 3. Start a new Claude Code session from your Godot project folder and ask: "Use ziva-godot's run scene tool to run res://main.tscn for 2500 ms, holding ui right from 300 ms for 1200 ms, and tell me which errors it printed." Cursor cursor 1. Under AI application , choose Cursor and click Install for Cursor . Ziva adds ziva-godot under mcpServers in your project's .cursor/mcp.json . 2. Open that same project folder in Cursor and restart Cursor. 3. Ask Cursor to use ziva-godot's run scene on a scene, as in the Claude Code example. If Godot is closed, a command-line client such as Claude Code started from your project folder sees one Ziva tool, start godot , which opens the editor; after that, the full Ziva tool list appears. Codex, VS Code, Windsurf, Zed, Gemini CLI and other apps have their own Install for app button, and the Ziva MCP server guide https://ziva.sh/docs/ziva-mcp-server has the manual setup. What Ziva's MCP tools return what-zivas-mcp-tools-return Ziva's run scene takes a scene path, a run length in duration ms and an optional list of timed inputs. Each input starts at at ms and is held for hold ms : Ziva's input types are action a named input action , key a raw keyboard key, with Shift, Ctrl, Alt or Meta held as modifiers , mouse a left or right click at a pixel position , target a click on a Control found by node path or visible text and motion relative mouse movement, for a camera with a captured mouse . Ziva's run scene returns: - One screenshot: the final frame of the running game, as an image Claude Code or Cursor can look at. - An input delivery report with the frame and millisecond each press and release landed on, so the client can tell an input the game never got from one it ignored. - The Godot console output and runtime errors from that run, with file and line. - With speed: true , the frame rate, and when the run is slow, the slowest functions with file and line. Ziva's other tools for this loop are get godot errors for script errors, runtime errors, stack traces and print output, get screenshot for the editor window or its 2D or 3D viewport, get scene tree to inspect the scene, and run tests for a test suite. MCP calls skip Ziva's approval prompts, so use your client's permission settings. In our Godot playtesting guide https://ziva.sh/blogs/godot-automated-playtesting what-zivas-run scene-returned-on-star-catcher , Ziva's run scene held ui right in a sample game and returned the null-instance error from res://main.gd:15 with a screenshot showing the score still at 0. Tested: Claude Code running a Godot game through Ziva's MCP server tested-claude-code-running-a-godot-game-through-zivas-mcp-server On 7 November 2026 we connected Claude Code 2.1.318 to Ziva's MCP server with the same stdio command Ziva's Install for Claude Code button registers, opened the Star Catcher sample https://github.com/ziva-sh/ziva-godot-sample in Godot 4.7.2 with a development build of Ziva from 7 November 2026 and the Ziva dock signed in to a Hobby account, and ran one prompt: Use the ziva-godot MCP tools. Run the main scene of this Godot project for about 4 seconds while holding the right arrow key ui right for 2 seconds, then tell me what the screenshot shows and list any runtime errors exactly as reported. Do not edit any files. Claude Code saw 42 ziva-godot tools, read the main scene path with Ziva's get project info , then called Ziva's run scene once: The call took 8.1 seconds. Ziva's input delivery report said the press landed at 0 ms and the release at 2009 ms, and Ziva's run scene returned the sample's two real errors word for word: From the screenshot and the errors, Claude Code concluded that a star was collected but the score label never updated, which is the bug. With Godot closed, the same Claude Code setup saw only Ziva's start godot tool, called it, and had the editor open with all Ziva tools available 5.2 seconds later; the first run scene after that hit a one-off upload error and worked on retry. With the Ziva dock signed out, Ziva's run scene and get screenshot returned "Not signed in", while Ziva's get godot errors and get project info still worked. What Ziva's MCP server can't do what-zivas-mcp-server-cant-do - Ziva's run scene returns one frame per call, not a video or a stream. To see a later moment, call it again with a longer duration ms . - Ziva's run scene needs the Godot editor open, so Ziva has no headless or CI mode. - Ziva's run scene has no gamepad or touch input. - Ziva's run scene refuses to start while you are playing a game in the editor, because it would close your game. - Ziva's Full Game Playtest Agent, which plays toward a goal and returns pass, fail or blocked, is not available over MCP. - Ziva's run scene and get screenshot need the Ziva dock signed in, because Ziva uploads each screenshot to Ziva's servers before returning it. Signed out, they return "Not signed in". - Ziva's run scene only appears when Enable playtest tool is on in Ziva's Settings → Agent . Ziva's generate image tool draws on your plan's included usage. How to choose a Godot MCP server how-to-choose-a-godot-mcp-server - Pick Ziva if you also want an AI agent inside the Godot editor, or you don't want to install Node.js or uv. Ziva's run scene gives Claude Code or Cursor input, a screenshot and errors in one call. - Pick Godot AI hi-godot/godot-ai if you are on Godot 4.7 or later and want a free, MIT-licensed server with gamepad input. - Pick Erodenn/godot-mcp-runtime if you want a free, MIT server with no addon to install or commit, or the game launched without the editor open. - Pick Coding-Solo/godot-mcp if you only need to run the project and read errors, with no editor addon. - Pick Godot MCP Pro or GDAI MCP if you prefer a one-time purchase: Godot MCP Pro lists mouse input and needs Godot 4.4 or later, and GDAI MCP lists keys and input actions. - For CI , use scripted GUT or GdUnit4 input tests rather than an MCP client; our playtesting guide https://ziva.sh/blogs/godot-automated-playtesting has tested examples. Related reading related-reading - Ziva as an MCP server https://ziva.sh/docs/ziva-mcp-server : full setup for every supported app - How to automate playtesting in Godot https://ziva.sh/blogs/godot-automated-playtesting : GUT, GdUnit4, headless bots and AI agents - Ziva vs Godot MCP https://ziva.sh/blogs/ziva-vs-godot-mcp : Ziva compared with Coding-Solo and other open-source servers - Ziva vs GDAI MCP https://ziva.sh/blogs/ziva-vs-gdai-mcp : Ziva compared with GDAI MCP