How to let coding agents drive Unreal, Godot and Minecraft with MCP

Coding agents such as Claude Code and Codex can now work inside game engines, not just edit their files, through the Model Context Protocol (MCP). The biggest example is Unreal MCP, an experimental plugin in Unreal Engine 5.8 that, according to Epic's documentation, runs an MCP server inside the editor so an agent can spawn actors, set up lighting and run automation tests.

An MCP server publishes an app's functions as named tools that the agent can call, then read back what happened. In an October 6 blog post, Sentry's Ivan Tustanivskyi wrote that agents could previously read and write a project's C++ while the editor stayed "a black box to them."

How it works

• Enable a server for your engine. In Unreal 5.8, Epic's docs say to turn on the Unreal MCP and All Toolsets plugins (without the second there are no tools) and start the server, which listens on 127.0.0.1:8000/mcp by default.
• Register it with your agent. The console command ModelContextProtocol.GenerateClientConfig writes the config for Claude Code, Cursor, VS Code, Gemini or Codex.
• Let the agent look, act and check: read the state, make a change, then read the result, often as a screenshot.
• Add your own tools. Epic documents how to define them in C++ or Python; they appear alongside the built-in ones.

Sentry did exactly that: its Unreal plugin (1.24.0 or later) registers editor tools and agent skills for setup, symbol upload, instrumentation and crash debugging. Other engines rely on community servers. According to their READMEs, Godot Agent Kit, posted to GitHub on October 28, gives an agent live control of the Godot 4 editor and a running game, including screenshots and QA play-testing, and MCP Fabric, a Minecraft: Java Edition mod for Fabric and NeoForge, offers more than 50 tools to move, build, inspect the world and take screenshots.

Playgama's MCP server, which GamesBeat reported on October 14, lets an agent upload a game to Playgama's sandbox, and Playgama's developer docs list tools for reading its custom-event telemetry afterward.

Why it matters

An agent that can only edit text has to guess what the engine is doing. An engine server lets it build, run the game and see what broke, the same loop behind our earlier story "6 open-source tools let coding agents playtest and check the games they build."

Limits and caveats

Epic labels Unreal MCP experimental, and its docs say the server has no authentication and isn't safe to expose beyond your own machine. It binds to localhost by default, so keep it there. Sentry reported two rough edges: agents sometimes skip tool discovery and edit project files by hand, and they lose their tools when the editor restarts. Epic's server shows three discovery tools by default to save context. AIGamer hasn't tested these servers.

How to try it

Start with the engine's official server where one exists, and make sure the agent can see its own work. On Unreal, an always-on proxy helps: charnet3d's unreal-mcp-bunny caches the editor's tools through restarts and recompiles, and diegoperini's Windows-only UnrealMcpProxy stays up when the editor crashes or recompiles. Sentry also recommends Epic's Unreal Engine skills plugin for Claude Code, which it said reduced extra prompting. Sentry calls this a first iteration and expects Unreal MCP and its skills to keep changing.