THE 2026 SHORTLIST

The right MCP for your kind of building.

Start with a useful workflow, not the longest tool list. These are our four editorial picks from a wider GitHub review.

Documentation reviewed October 10, 2026. Editorial recommendations, not hands-on benchmarks.

Our editor pick

Godot AI

hi-godot/godot-ai

Work with scenes, scripts, signals, and the live Godot editor.

Why this pick: Live scene editing · GDScript validation · Client setup in the editor.

The trade-off: Requires an editor addon. C# editing is text-only; .NET builds and compiler diagnostics are separate.

Read a relevant issue: Asset reimport report · v4.2.1
For runtime checks

Godot MCP Runtime

Erodenn/godot-mcp-runtime

Run a game, capture its screen, simulate input, and inspect what changed.

Why this pick: Runtime screenshots · Input simulation · Headless scene editing.

The trade-off: Uses a temporary runtime bridge and updates .gitignore. It helps verify behavior; human playtesting is still needed.

Read a relevant issue: Godot stdout / JSON report
For broader control

Godot MCP Full Control

tugcantopaloglu/godot-mcp

Headless project tools, runtime inspection, and C# project scaffolding.

Why this pick: Project scaffolding · GDScript diagnostics · C# project setup.

The trade-off: Source build required. Runtime tools need an autoload; check client schema compatibility before adopting a release.

Read a relevant issue: VS Code schema report · v3.1.0
For a basic connection

Godot MCP

Coding-Solo/godot-mcp

A focused starting point for launching Godot and reading debug output.

Why this pick: Launch and stop projects · Capture debug output · Basic scene operations.

The trade-off: Narrower runtime capabilities and an older push date. The highest Star count is not a reliability guarantee.

Read a relevant issue: Maintenance discussion

How we choose tools

We prioritize a clear development use case, documented setup, recent maintenance signals, and visible limitations. Stars provide context, not a quality score. Godot AI leads our live-editor shortlist; Runtime leads the runtime-verification use case. Your existing project or client can change the best choice.

We searched GitHub’s repository index, captured the first 30 results for “godot mcp” in names and descriptions, and examined the featured projects’ READMEs, release records, and recent issues. Snapshot: October 10, 2026. The search is not an exhaustive inventory.

Features and compatibility reflect upstream documentation. We have not benchmarked these MCPs or installed them into a test game. An open issue is a reported case, not proof that every current release is affected. Release packages and the default branch can contain different fixes.

Other projects worth knowing

fennaraOfficial/fennara-godot-ai

303 Stars · last push 2026-10-09

MCP connection plus an optional in-editor chat dock; Godot 4.5+.

Addon, CLI, and local daemon; supported desktop architectures vary.

satelliteoflove/godot-mcp

173 Stars · last push 2026-10-02

Editor tools and deterministic runtime checks; Godot 4.5+ and Node.js 20+.

Requires an addon. A useful specialist option to evaluate for test workflows.

IvanMurzak/Godot-MCP

277 Stars · last push 2026-10-10

C# editor integration, with a cloud connection option.

Apache-2.0 project; review .NET and service requirements.

youichi-uda/godot-mcp-pro

620 Stars · last push 2026-09-24

Editor tooling with a separately distributed paid MCP server.

The public repository contains the addon, not the complete paid server. No mirror offered.

tomyud1/godot-mcp

433 Stars · last push 2026-08-24

MCP server with a Godot editor plugin.

Additional option; compare its setup and engine requirements with your project.

DaxianLee/godot-mcp

544 Stars · last push 2026-01-14

Godot editor addon with client configuration support.

License needs individual review before redistribution.

ee0pdt/Godot-MCP

617 Stars · last push 2025-03-19

An earlier Godot MCP implementation.

Older push date; not a default recommendation for a new setup.

Downloading is the beginning.

Verify a scene read, one saved edit, and one project run before relying on a tool for a larger change.

Follow the first workflow