Godot MCP Servers Compared: Six Ways to Connect AI to Godot

A Godot MCP server lets an AI client such as Claude Code, Cursor or Cline call tools in your Godot project: run it, read its errors, or edit its scenes. There are now several servers, and they differ most in one thing: whether they run outside the editor or inside it. This guide compares six of them from their own pages, and says which one we installed and tested.

The short answer

• You want the AI to run your project and read its errors: start with Coding-Solo’s godot-mcp. It is free (MIT), runs outside the editor through npx, and is the one our Godot MCP setup guide walks through.
• You want the AI to work inside the open editor and the running game (inspect live nodes, take screenshots, simulate input): look at an editor plugin. Godot MCP Toolkit and Funplay MCP are free (MIT); Godot MCP Pro is paid.
• You want no Node.js at all: Godot MCP Native runs entirely inside Godot, but its listing marks the download as unstable.

Three ways a server reaches Godot

A separate process. The AI client starts the server itself, usually with npx. The server drives Godot from the command line, so it works with the editor closed. Coding-Solo’s server works this way.

An editor plugin plus a Node bridge. A plugin in your project opens a local WebSocket inside the running editor, and a small npm package that the client starts connects to it. The AI can then act on the scene you have open. Godot MCP Toolkit and Godot MCP Pro work this way.

An editor plugin on its own. The plugin serves MCP itself, over HTTP on your machine, with no separate server to install. Godot MCP Native works this way. Funplay MCP also runs its server inside the editor, but recommends a small npm wrapper for the connection.

Coding-Solo’s godot-mcp

• Connects: a separate process the client starts with npx @coding-solo/godot-mcp. It runs Godot’s command line, with a bundled GDScript file for scene operations.
• Needs: Godot installed, and Node.js 18 or later.
• Licence: MIT, free.
• Can do: launch the editor, run a project in debug mode and capture its output, stop it, read the Godot version and project info, list projects, create scenes, add nodes, load sprites, export a MeshLibrary, save scenes, and read or update UIDs (Godot 4.4+).
• Not listed: editing scripts, screenshots or tests.
• Clients named: Claude Code, Cursor, Cline and other MCP clients. Claude Code setup is one command: claude mcp add godot -- npx @coding-solo/godot-mcp. Our setup guide adds -y so npm installs the package without asking.

This is the simplest to set up and the easiest to reason about, because it only touches what you ask it to run or write. Our setup guide has copyable configs for each client and the errors people hit most.

Godot MCP Toolkit

• Connects: an editor plugin listens on 127.0.0.1 (ports 6550 to 6560), and the npm bridge @npgamedev/godot-mcp-server connects to it. The plugin can write the client’s .mcp.json for you.
• Needs: Godot 4.2 or later (4.5+ recommended, tested up to 4.7), Node.js 22 or later, and a desktop OS.
• Licence: MIT, free.
• Can do: scenes and nodes, scripts with GDScript validation and LSP diagnostics, resources, animation and audio, playtests with live-node inspection, simulated input and screenshots, breakpoints and crash diagnostics. Its page counts up to 112 tools in 28 groups, most loaded on demand.
• Clients named: tested mainly with Claude Code; any MCP client.

Godot MCP Native

• Connects: runs entirely inside Godot with no Node.js, over HTTP at http://localhost:9080/mcp by default (an auth token is optional), or over stdio. Claude Desktop needs the mcp-remote npm package to reach the HTTP endpoint.
• Needs: Godot 4.x, 4.5 or later recommended. Its sidebar says 4.6 minimum, so check before you install.
• Licence: MIT, free.
• Can do: nodes, scenes, scripts (GDScript and C#), editor screenshots, debugger breakpoints, runtime input and screenshots, project settings and tests. The listing says 155 tools.
• Note: the store listing marks the download as unstable and says the code was written with AI. Version 1.0.8 was the latest on the page, updated July 30, 2026.

If you enable it, turn on the auth token: an HTTP endpoint on your machine can be reached by other programs running on it.

Godot MCP Pro

• Connects: an editor plugin and a Node.js server, over WebSocket port 6505.
• Needs: Godot 4.4 or later and Node.js 18 or later.
• Licence and price: the free Asset Library download is the editor plugin only. Its listing says the full package with the server costs $15 once, with lifetime updates, and marks it proprietary.
• Can do: 163 tools in 23 categories by its own count, from scenes and scripts to animation trees, physics, tilemaps, shaders, profiling and testing. A Lite Mode exposes 76 core tools.
• Clients named: Claude Code, Cursor, Windsurf, VS Code with Cline. Version 1.16.0, August 2026.

GDAI MCP

• Connects: an editor plugin; its GitHub page points to gdaimcp.com for the server command and install steps.
• Needs: Godot 4.1 or later.
• Licence: not open source. The repository says all rights reserved, and the plugin comes from gdaimcp.com.
• Can do: create scenes, nodes, resources and scripts; edit node properties; read debugger output and script errors; search project files; and take screenshots of the editor and the running game.
• Clients named: Cursor, Claude Desktop, VS Code (Copilot, Cline, Roo Code) and Windsurf.

Funplay MCP for Godot

• Connects: a local server inside the editor, bound to 127.0.0.1. The recommended connection is its npm wrapper, npx -y funplay-godot-mcp. Since version 0.9.1 each project needs an auth token for local requests.
• Needs: Godot 4.2 or later (tested on 4.6.3), and Node.js 18 or later for the wrapper. Works with GDScript and C# projects.
• Licence: MIT, free.
• Can do: inspect scenes and nodes, create and patch scripts, help build Control UIs, read and write project files under the project root, inspect the scene tree in play mode, and run release-readiness checks.
• Note: version 0.9.2 (June 2026); the store listing marks the download as unstable.

Before you let any of them change your project

• Commit your project to version control first. Running a project executes its code, and scene or script tools write files.
• Start by approving each tool call. Turn on automatic approval only for read-only tools, such as reading the version or project info.
• Prefer servers that bind to 127.0.0.1, and use an auth token where the server offers one.
• Check which Godot version the server was tested on. Several of these projects change every few weeks.

An MCP server gives the AI tools, not knowledge of Godot 4. Pair it with a Godot-aware agent file from our AI tools page, and check generated GDScript against the pitfalls in where LLMs get GDScript wrong.