Game engine agent tooling compared: Unreal, Unity, Godot, Roblox and Bevy

How a coding agent reaches into Unreal Engine, Unity, Godot, Roblox Studio and Bevy: the official MCP servers and CLIs, the main community servers, what each one runs on, how it is secured, how many tools it exposes and which ones are deprecated or inactive.

Type: Comparison
Author: Agentica Author
Published: 2026-10-31
Last verified: 2026-10-31

game-engine
gamedev
mcp
unreal-engine
unity
godot
roblox
bevy
editor-automation

Comparison

Game engine agent tooling compared: Unreal, Unity, Godot, Roblox and Bevy
Entry	Maintainer	Engine versions	Setup	Transport and local security	Tool surface	Status	Licence
Unreal MCP (Unreal Engine)	Epic Games (ModelContextProtocol plugin shipped with the engine)	Unreal Engine 5.8, marked Experimental	Enable the plugin (needs All Toolsets), start with Auto Start Server or ModelContextProtocol.StartServer, then ModelContextProtocol.GenerateClientConfig writes the client config	HTTP and SSE at http://127.0.0.1:8000/mcp; loopback only, rejects non-loopback Origin, no authentication	Toolsets written in Python or C++; Tool Search (on by default) exposes list_toolsets, describe_toolset and call_tool instead of every tool	Experimental in UE 5.8; tool calls run one at a time on the game thread	Part of Unreal Engine
Unity CLI	Unity Technologies	Pipeline package needs Unity 6.0 LTS or later	Install the unity binary, then unity pipeline install; unity mcp configure <client> or unity setup claude / codex / grok / antigravity	Shell commands (unity command, unity eval) or an MCP mode; the pipeline server is localhost-only and works offline	CLI commands plus MCP tools, filterable with unity mcp --tools / --exclude-tools globs	Experimental; 1.0.0-beta.14 (2026-10-21). Replaces the deprecated AI Assistant MCP server	Free, no Unity AI subscription needed (licence not stated in the docs)
MCP for Unity	CoplayDev community project, not affiliated with Unity	Unity 2021.3 LTS to 6.x; Python 3.10+ via uv	Add the package from the git URL or OpenUPM, then Window > MCP for Unity > Configure All Detected Clients	Client over stdio or HTTP /mcp to a Python FastMCP server, which talks WebSocket to the C# Editor plugin; optional remote auth	48 tool entrypoints with tool groups, multi-instance support and Roslyn validation	Active; v10.3.0 (2026-10-04), 15.5k stars	MIT
Godot AI	hi-godot community project	Godot 4.7+; needs uv	Install the editor plugin; its dock configures 26 clients, which connect through godot-ai attach (stdio)	Python server on authenticated HTTP port 8000 and WebSocket port 9500, both on loopback; a bare HTTP POST returned 401 in our test	README: 46 tools and 120+ operations; attach listed 47 tools in our test	Active; v4.3.1 (2026-10-24), signed releases. Disabled in headless editors unless GODOT_AI_ALLOW_HEADLESS=1	MIT
Godot Editor MCP (hybridindie/godot-mcp)	hybridindie community project	Godot 4.4+, validated on 4.7; Python 3.11+	pip install godot-editor-mcp or uvx, plus the godot_mcp editor addon; godot-editor-mcp config --client <x> --write	stdio or HTTP on 127.0.0.1:9090; addon dials ws://127.0.0.1:9080 with an optional bridge token; foreign Host 421, foreign Origin 403; auth token required for non-loopback binds	201 tools in 29 categories; only core and inspection are on by default (24 tools in our test), more via godot_enable_toolset	Active; 2026.10.20.1 on PyPI and GitHub	MIT
Beckett (Godot MCP)	Beckett Lab (free Lite edition; paid Full edition)	Godot 4.2+ (4.4+ recommended)	Copy the addon and enable it; it starts the server and writes .mcp.json itself	Streamable HTTP served by a GDScript plugin on 127.0.0.1:8770, no sidecar; per-project token in the URL path, exact Host and Origin checks	Lite: 56 tools, 6 resources, 6 prompts; optional read-only mode, allowlist and destructive-call confirmation	Active; v1.16.0 (2026-10-06), 47 stars	MIT (Lite); Full edition is a $15 one-time purchase
Roblox Studio MCP server	Roblox (built into Studio)	Current Roblox Studio	Assistant > Manage MCP Servers > Enable Studio as MCP server, then quick connect a client or point it at the StudioMCP command	Local process over stdio; every tool takes a studio_id, list_roblox_studios lists open instances	Script read, edit, search and grep, Luau execution, play control, screen capture, input simulation, asset search and insert, mesh and material generation, subagents	Current; replaces the archived studio-rust-mcp-server	Part of Roblox Studio
bevy_brp_mcp	natepiano community project, not an official Bevy project	Bevy 0.20 (crate 0.23.0); older crate versions map to Bevy 0.16 to 0.19	cargo install bevy_brp_mcp, add it as a stdio server, and add RemotePlugin with the bevy_remote feature to the game	stdio to the agent; talks to the running game over the Bevy Remote Protocol (HTTP transport defaults to port 15702)	Entities, components, resources, queries, hierarchy, type guide, app discovery and launch, logs; screenshots and input with bevy_brp_extras	Active; 0.23.0 (2026-10-09)	MIT OR Apache-2.0

Verdict: Use the engine vendor's path where one exists: Unreal MCP in UE 5.8, the Unity CLI in Unity 6 (not the deprecated AI Assistant MCP server) and Studio's built-in server in Roblox. On Unity versions before 6, CoplayDev's unity-mcp is the mature option. On Godot, pick Beckett for a no-sidecar plugin, Godot AI for the widest client setup, or Godot Editor MCP for the largest opt-in toolset. For Bevy, bevy_brp_mcp drives the running game.

The first agent bridges for game engines were community projects, such as the two Unreal servers below, which drive the editor over a TCP socket or Python remote execution. Now Epic and Roblox ship MCP servers inside their editors, Unity has moved from its own MCP server to a CLI, and Godot has three serious community servers. This page compares the current options for each engine. Every version, date and count was checked on 2026-10-31 against vendor docs, the repositories and the package registries. We also ran all three Godot servers against a headless Godot 4.7.2 editor; Drive a headless Godot editor over MCP has the commands and results.

Unreal Engine: Epic's plugin replaces the community bridges

Unreal MCP is an Experimental plugin (ModelContextProtocol) in Unreal Engine 5.8. It depends on the All Toolsets plugin and enables the Toolset Registry. Turn on Auto Start Server in its settings or run ModelContextProtocol.StartServer [port] in the console. The server listens at http://127.0.0.1:8000/mcp. ModelContextProtocol.GenerateClientConfig takes ClaudeCode, Cursor, VSCode, Gemini, Codex or All and writes the client config for you. For CI or scripted launches there are the -ModelContextProtocolStartServer and -ModelContextProtocolPort=N command-line flags.

Points that matter for agent work:

Transports are HTTP and SSE only. There is no stdio, so a client that only speaks stdio needs a bridge (see Bridge stdio and remote MCP servers).
There is no authentication. The server only accepts loopback connections and rejects non-loopback Origin headers. Epic's docs say it is not safe to expose beyond the local machine.
Tool Search is on by default. tools/list returns three meta-tools (list_toolsets, describe_toolset and call_tool), and the agent discovers the real tools through them. This keeps a large toolset out of the context window, but agents that expect a flat list need a prompt nudge.
Calls run serially on the game thread. Long tool calls block the editor.
You can add your own tools in Python (unreal.ToolsetDefinition with @toolset_registry.tool_call) or C++ (UToolsetDefinition with UFUNCTION(meta=(AICallable))), and reload them with ModelContextProtocol.RefreshTools. MCP resources and prompts are not advertised.

Epic also publishes Unreal Engine skills for Claude Code, an MIT plugin installed with /plugin install unreal-engine-skills-for-claude-code@claude-plugins-official. Its README describes "hundreds of tools … across 30+ toolsets". Our own Unreal Engine development skill covers the build, test and editor-scripting side.

The two well-known community servers are both inactive. runreal/unreal-mcp (MIT) drives the editor through Python Remote Execution and needs no extra plugin, but its last push was in June 2025 (npm 0.1.4). chongdashu/unreal-mcp has 2.1k stars but no licence file (GitHub reports none, although the README badge says MIT), and its last push was in April 2025. For anything new on UE 5.8, start with Epic's plugin. On older engines, scripting through the Unreal Python API is the maintained path.

Unity: the CLI replaces Unity's own MCP server

The Unity AI Assistant MCP server is deprecated. The notice first appears in the AI Assistant 2.18 docs ("Unity MCP server is deprecated. Use the Unity command-line interface (CLI) instead.") and is absent from the 2.17 docs.

The replacement is the Unity CLI, currently experimental at 1.0.0-beta.14 (2026-10-21). unity pipeline install adds the Pipeline package to a project (Unity 6.0 LTS or later). Then either:

call the Editor from the shell with unity command and unity eval, which Unity's docs say are faster and use fewer tokens than MCP, or
keep MCP: unity mcp configure <client> writes the config for claude, cursor, vscode or windsurf (--list shows the rest), and beta.14 adds --tools and --exclude-tools glob filters plus --port, --pid and --instance to pin a specific running Editor.

unity setup claude, unity setup codex, unity setup grok and unity setup antigravity do the per-agent setup in one step. The pipeline server listens on localhost only and works offline, and the CLI does not need a Unity AI subscription. Unity's docs say third-party MCP packages are unaffected by the deprecation. If you also run AI Assistant, use version 2.13 or later, which fixes a conflict with the CLI.

We could not install the CLI with the documented one-liner on 2026-10-31: the install script stopped with "Failed to fetch version manifest" because the stable manifest it requests returned 404. Its beta channel manifest did load. We did not get as far as an Editor, so the Unity rows come from Unity's docs only.

Unity's skills repository (35 skills, Unity Companion License, npx skills add Unity-Technologies/skills) adds Unity-specific instructions for any agent that reads skills; see Agent skill packs and installers.

The main community option is CoplayDev's MCP for Unity, which is MIT, has 15.5k stars and was at v10.3.0 on 2026-10-04. It supports Unity 2021.3 LTS through 6.x, so it is the choice for projects that cannot move to Unity 6. The client talks stdio or HTTP to a Python FastMCP server (run by uv), which talks WebSocket to a C# Editor plugin. It exposes 48 tool entrypoints, with tool groups to trim them, and supports several Editor instances. It is not affiliated with Unity Technologies.

Godot: three community servers with different designs

None of the three active Godot servers comes from the Godot engine project itself; all are community plugins. We installed all three into fresh projects and drove a headless 4.7.2 editor with each.

Godot AI (MIT, v4.3.1) has the most polished setup. Its dock configures 26 clients, and clients connect through godot-ai attach over stdio. The plugin starts a Python server with authenticated HTTP on port 8000 and an authenticated WebSocket on port 9500, both on loopback. Because of that authentication, the README warns that a bare http://127.0.0.1:8000/mcp entry cannot authenticate, and our bare POST got 401. It needs Godot 4.7+ and uv, and it sends anonymous telemetry unless you set GODOT_AI_DISABLE_TELEMETRY=true. In a headless editor it stays off unless GODOT_AI_ALLOW_HEADLESS=1 is set.
Godot Editor MCP (MIT, 2026.10.20.1 on PyPI) is a Python server (pip install godot-editor-mcp) plus an editor addon that dials it on ws://127.0.0.1:9080. It has 201 tools in 29 categories, but only core and inspection are enabled at first, so tools/list returned 24 tools for us. The agent turns on more with godot_enable_toolset. Mutating tools take dry_run. Its HTTP mode on 127.0.0.1:9090 answered a foreign Host header with 421 and a foreign Origin with 403, and it requires an auth token before it will bind to a non-loopback address.
Beckett (MIT Lite edition, v1.16.0) has no sidecar at all. A GDScript editor plugin serves Streamable HTTP on 127.0.0.1:8770, starts when the plugin is enabled, and writes .mcp.json for you. The per-project token is part of the URL path. It exposes 56 tools, 6 resources and 6 prompts, and validates scripts before writing them. In our test it refused a script with a parse error. Environment variables switch on read-only mode (BECKETT_READONLY=1), a tool allowlist or confirmation for destructive calls. A paid Full edition ($15 one-time) adds more tools, skill packs and playtesting.

Beckett is the least moving parts, Godot AI the easiest for a team on many clients, and Godot Editor MCP the most tools with the tightest default context.

The most-starred Godot server, Coding-Solo/godot-mcp (MIT, about 6.4k stars), works differently. It is a Node.js server that launches the editor, runs projects, captures debug output and edits scenes. Its last push was in April 2026, so we left it out of the table.

Roblox Studio: built in, stdio, multi-instance

Roblox Studio's MCP server is part of Studio. Enable it under Assistant > Manage MCP Servers > Enable Studio as MCP server. Quick connect covers Antigravity, Codex CLI, Claude Code, Claude Desktop, Cursor, Gemini CLI and VS Code. Any other client can run the local StudioMCP process over stdio: /Applications/RobloxStudio.app/Contents/MacOS/StudioMCP on macOS, or cmd.exe /c %LOCALAPPDATA%\Roblox\mcp.bat on Windows.

Every tool takes a studio_id, and list_roblox_studios returns the open Studio instances, so one agent can work across several places. The tools go well beyond editing scripts. They include execute_luau, start_stop_play, screen_capture, simulated keyboard and mouse input, asset search and insertion, mesh, material and procedural-model generation, and a subagent tool for exploring or playtesting. The earlier open-source studio-rust-mcp-server (MIT) is archived, and its README says it is no longer actively developed.

Bevy: drive the running game

Bevy games are plain Rust code, so agent tooling attaches to the running app rather than to an editor. bevy_brp_mcp is a stdio MCP server (cargo install bevy_brp_mcp) that speaks the Bevy Remote Protocol. Add RemotePlugin and enable Bevy's bevy_remote feature, and the agent can find, build and launch your apps and examples, then query and change entities, components and resources while the game runs. Bevy's HTTP transport for the protocol listens on port 15702 by default. The optional bevy_brp_extras plugin adds screenshots, keyboard, mouse and gamepad input, and diagnostics. Crate 0.23.0 targets Bevy 0.20. It is a community project, not an official Bevy one.

Security notes that apply to all of them

Keep these servers on loopback. Unreal's plugin has no authentication at all. Beckett and Godot AI use tokens, and Godot Editor MCP checks Host and Origin, but none of them is designed to be exposed to other machines. Run Test your MCP server-style probes to confirm what an endpoint accepts before you trust it.
Don't commit generated client configs that hold secrets. Beckett writes its token into .mcp.json and .cursor/mcp.json.
These tools can run arbitrary engine code. Unreal toolsets run Python and C++, Roblox has execute_luau, and several Godot tools write and attach scripts. Treat an agent with these tools as having full access to the project and to the user account that runs the editor.

Directory entries in this comparison

Unreal MCP (Unreal Engine): Epic's experimental Unreal Engine 5.8 plugin that embeds a local HTTP MCP server in the Unreal Editor so agents can drive editor functionality.
Unity CLI: Unity's experimental command-line interface for installing Editors and modules, managing projects and driving a running Editor, with an MCP mode for agents.
MCP for Unity: MIT bridge between MCP clients and the Unity Editor: 50 tools to create scenes and GameObjects, edit C# scripts, manage assets, run tests and build.
Godot AI: Godot editor add-on plus a Python MCP server that connects Claude Code, Codex, Cursor and other clients to a live Godot editor through 46 tools.
Godot Editor MCP (hybridindie/godot-mcp): Game-agnostic MCP server plus a Godot add-on that drives a live editor: inspect, edit scenes and scripts, run, simulate input, screenshot, profile and export.
Beckett (Godot MCP): Zero-sidecar MCP server that runs inside the Godot 4 editor as a GDScript plugin, letting agents inspect, author, run and screenshot a game in GDScript or C#.
Roblox Studio MCP server: Built-in MCP server in Roblox Studio that lets AI clients explore the data model, read and edit scripts, run Luau, generate assets and playtest.
bevy_brp_mcp: Community MCP server that lets coding agents launch, inspect and change running Bevy apps over the Bevy Remote Protocol.
Unity MCP server (AI Assistant package): Deprecated in-Editor MCP server in Unity's com.unity.ai.assistant package. External MCP clients reach Unity tools through a relay. Unity says to use the Unity CLI instead.
Unity Skills: Unity's official agent skills for Unity workflows such as monetization, 2D art and Editor installs. Install with `npx skills add Unity-Technologies/skills`.
Unreal Engine Skills for Claude Code: Epic's Claude Code plugin with an unreal-mcp skill and a SessionStart hook for driving the Unreal Editor through its built-in MCP server.
runreal unreal-mcp: Community MCP server for Unreal Engine that uses the built-in Python remote execution protocol, so no extra UE plugin is needed.
unreal-mcp (chongdashu): Experimental community project (UE plugin plus Python MCP server) letting Cursor, Windsurf or Claude Desktop control Unreal Engine actors and Blueprints.
Unreal Python API: Epic's Python API for scripting the Unreal Editor (content production and pipeline tasks); an experimental feature also used by community MCP servers.
Godot Engine: Free, open-source, multi-platform 2D and 3D game engine, scripted in GDScript or C#. Several community MCP servers let agents drive its editor.
Bevy: Free, open-source, data-driven game engine in Rust built on an entity component system (ECS).
Model Context Protocol (MCP): Open protocol that standardizes how AI applications connect to external tools, data sources and prompts via MCP servers.

Drive a headless Godot editor over MCP (Guide)
Unreal Engine development for coding agents (Skill)
Agent skill packs, skills CLIs and registries (Comparison)
Bridge stdio and remote MCP servers: mcp-remote, Supergateway, mcp-proxy and mcpo (Guide)
Test your MCP server with in-process tests and Inspector CI checks (Guide)

Sources

Unreal MCP in Unreal Editor (Epic docs), accessed 2026-10-31
Unreal Engine skills for Claude Code plugin (EpicGames), accessed 2026-10-31
Unity CLI docs, accessed 2026-10-31
Unity CLI: replace the MCP server with the Unity CLI, accessed 2026-10-31
Unity CLI release notes, accessed 2026-10-31
Use the Unity CLI, accessed 2026-10-31
Unity AI Assistant 2.18 docs, Unity MCP overview (deprecation notice), accessed 2026-10-31
Unity AI Assistant 2.17 docs, Unity MCP overview (no deprecation notice), accessed 2026-10-31
Unity-Technologies/skills, accessed 2026-10-31
CoplayDev/unity-mcp, accessed 2026-10-31
CoplayDev/unity-mcp v10.3.0 release, accessed 2026-10-31
hi-godot/godot-ai, accessed 2026-10-31
Godot AI server lifecycle (headless note), accessed 2026-10-31
hybridindie/godot-mcp (Godot Editor MCP), accessed 2026-10-31
PyPI: godot-editor-mcp, accessed 2026-10-31
Coding-Solo/godot-mcp, accessed 2026-10-31
beckettlab/beckett-godot-mcp, accessed 2026-10-31
Roblox Studio MCP server (Creator docs), accessed 2026-10-31
Roblox/studio-rust-mcp-server (archived), accessed 2026-10-31
bevy_brp_mcp README, accessed 2026-10-31
crates.io: bevy_brp_mcp, accessed 2026-10-31
docs.rs: bevy_remote http module, accessed 2026-10-31
runreal/unreal-mcp, accessed 2026-10-31
chongdashu/unreal-mcp, accessed 2026-10-31