The Best Godot MCP Server in 2026 (Honest Roundup for Cursor and Claude)

Search "best Godot MCP server" and you get a list of GitHub repos with no opinion attached, which is not useful when you are in Cursor or Claude trying to decide what to install. This roundup ranks the real options by what they let your AI client do inside a Godot project, names the best pick for the common cases, and is honest about where Summer Engine fits. For install commands per client, the full Summer tool list, and troubleshooting, see the Godot MCP page.

{/* IMAGE: Hero graphic showing an MCP client (Cursor) connected by a bridge to a Godot project, with a "play" button and a runtime error being read back. 1200x630, illustration. */}

What an MCP server actually does for Godot

A Model Context Protocol server is a small program that exposes tools to an AI client over a shared standard. For Godot, that means a client like Cursor, Claude Desktop, Claude Code, Devin Desktop, or Cline stops being blind to your project. Instead of you pasting "I have a CharacterBody3D with these children and a script that does this," the server lets the AI read the structure itself.

There are roughly three tiers of Godot MCP server, and the ranking turns on the difference.

• File-level servers read and edit the files in your project. They parse .tscn scene files for structure, open and rewrite .gd scripts, and read project settings.
• Editor-level servers also drive the Godot editor: create scenes and nodes, run the project, and bring back debug output. Coding-Solo's godot-mcp and GDAI MCP are here in 2026.
• Engine-level servers add runtime control and generation: send input to the running game, probe state frame by frame, diff the world before and after a change, and generate assets that import into the project. Summer Engine's server is here.

The ranking

Ordered by how much each server lets the client do, not by GitHub stars. Where one is the right default, we say so plainly. Features are as listed on each project's README or website on 2026-09-25.

Coding-Solo/godot-mcp (best free option for the stock editor)

Type: Editor-level, MIT, npx Works with: Claude Code, Claude Desktop, Cursor, Cline, other MCP clients

Coding-Solo's godot-mcp launches the Godot editor for a project, runs the project in debug mode, captures console output and errors, creates scenes, adds nodes with properties, and loads sprites. It installs as a single npx entry (npx @coding-solo/godot-mcp), and the codebase is small enough to read before you trust it.

Where it stops: no screenshots or simulated input listed, and no asset generation.

Best for: developers who want a free, auditable server that works with the stock Godot editor.

GDAI MCP (most polished stock-editor plugin)

Type: Editor-level, Godot plugin, paid ($19 one-time per its website) Works with: Claude Desktop, Cursor, VS Code, other MCP clients

GDAI MCP installs as a plugin in your Godot 4.2+ project. It creates and edits scenes, nodes, resources, and scripts, reads debugger output and script errors, searches project files, takes screenshots of the editor and the running game, and can trigger keyboard input in the running game. The docs cover the common clients, and first-time setup is smooth.

Where it stops: it is paid, it lives in the stock editor only, and it does not generate assets.

Best for: developers who want the most complete plugin inside the editor they already use.

bradypp/godot-mcp and satelliteoflove/godot-mcp (community alternatives)

Type: Community, open source Works with: MCP clients per each README

bradypp/godot-mcp and satelliteoflove/godot-mcp are community-maintained takes on the same idea that evolve at their own pace, so check the current README before committing. For a first install, Coding-Solo's server and GDAI MCP are safer starting points.

Best for: developers comparing approaches or wanting a backup if a primary server stalls.

Summer Engine MCP (best for runtime control and generation)

Type: Engine-level, MIT, npx Works with: 31 agents via one setup command, including Claude Code, Claude Desktop, Codex, Cursor, Devin Desktop, Cline, Kilo Code, OpenCode, Zed, and LM Studio

Summer Engine is a desktop game engine compatible with Godot 4, and its MCP server lets an outside client drive it. The tool surface covers scene and script editing plus the runtime and generation groups: run the game, send input, probe the running game frame by frame, read diagnostics and debugger errors, take screenshots and world snapshot diffs, and generate 3D models, images, audio, video, and motion that import straight into the project. Cloud tools such as generation and asset search work even when the desktop app is closed.

When the client says "add a coin pickup with a HUD counter," it creates the Area3D, writes and attaches the script, instances the coins in the level, runs the game, and checks whether the count actually incremented. If the AI emits a Godot 3 call by mistake, the running engine throws, the error comes back, and the client corrects. Our Cursor plus Godot versus Summer Engine comparison walks that coin example on both stacks.

Honest limits: the engine tools drive the Summer Engine desktop app, not the stock Godot editor. If your work is writing and refactoring GDScript in an existing stock-Godot install, one of the servers above keeps you in the editor you know. You also do not need the MCP server to work inside Summer Engine; the agent is built in, and the server is for driving Summer from an outside client.

Best for: developers who want their MCP client to test the game like a player and generate the assets, not just edit scenes and scripts.

Side by side

	Coding-Solo	GDAI MCP	Summer Engine MCP
Where it runs	Stock Godot editor	Plugin in stock editor (4.2+)	Summer Engine app (compatible with Godot 4)
Create scenes and nodes	Yes	Yes	Yes
Run the game, read debug output	Yes	Yes	Yes
Screenshots of the running game	Not listed	Yes	Yes
Simulated input	Not listed	Yes	Yes, plus frame-stamped probes
Generate assets (3D, 2D, audio)	No	No	Yes
Install	npx entry per client	Plugin plus client config	One command writes the config
Cost	Free, MIT	$19 one-time	Free, MIT; generation uses credits

Read it by where your game lives. In the stock editor, the choice is Coding-Solo or GDAI. If you want generation and runtime probes in the same server, Summer Engine is the one that has them.

Honest free vs paid

Coding-Solo's server and the other community projects are free and open source. GDAI MCP charges $19 once, according to its website. Summer Engine's MCP server and CLI are free and MIT licensed: engine control and asset search cost nothing, and cloud generation uses credits, with current numbers on the pricing page. In every case your AI client bills its own model usage on top.

How to set up a Godot MCP server

The exact steps vary by server, but the shape is the same: add a server entry to your client config, restart the client, and ask "what scenes are in this project?" to confirm it is connected.

Coding-Solo's godot-mcp. In Claude Code: claude mcp add godot -- npx @coding-solo/godot-mcp. In Cursor or Cline, add an entry that runs npx @coding-solo/godot-mcp. You need Godot and Node.js 18 or newer installed.

GDAI MCP. Add the plugin to your Godot project, enable it, then add the MCP server command from its docs to your client.

Summer Engine. One command writes the config for your client, installs the agent skills, and runs a health check:

npx -y summer-engine@latest setup cursor --yes

Swap cursor for claude-code, claude-desktop, codex, windsurf, cline, or any of the other supported agents. The entry it writes is the same for every client:

{
  "mcpServers": {
    "summer-engine": {
      "command": "npx",
      "args": ["-y", "summer-engine@latest", "mcp"]
    }
  }
}

Open a project in Summer Engine so the engine tools have an engine to talk to, and run npx -y summer-engine@latest login once for the cloud tools. Per-client commands and troubleshooting are on the Godot MCP page.

How to pick in one pass

• You want a free server for the stock Godot editor: Coding-Solo's godot-mcp.
• You want the most polished stock-editor plugin and do not mind paying once: GDAI MCP.
• You are comparing approaches or want a backup: bradypp or satelliteoflove.
• You want the client to test the game like a player and generate assets: Summer Engine's MCP, ideally starting from a template for your genre.

For Godot specifically, where most bugs only surface at runtime, a server that can press play and read the real error will out-build one that edits text blind to the running game. In 2026 several can. The remaining differences are where the game lives, what it costs, and whether you want generation in the same loop.

If you want the wider picture, the best AI tools for Godot roundup covers the full landscape, the Godot AI agent guide goes deeper on what an in-engine agent can and cannot do, and the Godot AI page explains how Summer Engine builds the AI into the engine. If you would rather skip the external server entirely, you can download Summer Engine and start free.