# Game studios on Unreal Engine: keep MCP and build logs from filling your AI agent's context

> Unreal's MCP server gives your AI agent hundreds of editor tools and long logs to read. Tokenade folds big MCP results and build output locally.

Source: https://tokenade.net/en/solutions/software-teams/game-studios · Updated: 2026-10-16

Since Unreal Engine 5.8, your AI agent can drive the editor through MCP: list actors, edit Blueprints, compile, read the logs. Each of those calls returns text the agent must read, and a game project produces a lot of it. Tokenade folds the large results and the build output on your machine before they reach the model.

## What you deal with every day

Unreal now ships an official path for AI agents. UE 5.8, available since June 17, 2026, includes an Experimental MCP server inside the editor, so agents such as Claude Code, Codex and Cursor "can drive editor functionality over a local HTTP connection instead of you copy-pasting Output Log text between windows" ([gamineai.com, July 19, 2026](https://gamineai.com/blog/unreal-engine-5-8-mcp-claude-code-first-safe-editor-session-2026)).

That is a real step forward. It also means the editor's state and logs now flow straight into the agent's context.

### Hundreds of tools behind one server

Epic's plugin for Claude Code exposes "Hundreds of tools… across 30+ toolsets: actors, blueprints, materials, Niagara, Control Rigs, Sequencer" and more ([EpicGames on GitHub, last updated September 17, 2026](https://github.com/EpicGames/unreal-engine-skills-for-claude-code-plugin)). A third-party editor plugin advertises 1,655 native tools ([gamedevcore.com, read October 15, 2026](https://www.gamedevcore.com/solutions/unreal-engine-mcp)).

Epic's own design shows the weight of that catalogue. Its plugin enables "Tool search" by default, exposing three meta-tools "instead of the full tool catalog, so Claude discovers toolsets on demand, the prompt cache stays warm". That solves the catalogue. The results of each call still land in full.

### Build and editor logs are long

Unreal builds and editor sessions write long logs, and agents read them to diagnose failures. A community skill for UE5 work tells the agent, when a build fails, to "Read the last 50 lines of build output" rather than the whole thing ([UE5 Development skill on mcpmarket.com, read October 15, 2026](https://mcpmarket.com/tools/skills/ue5-development-debugging)).

That rule works when the error sits at the end. When it does not, the agent goes back for more, and every extra read stays in the conversation.

### Slow round-trips and an unclear bill

Early users of the 5.8 integration report friction. "It's slow and when paired with the already existent message batching delays with Claude Code, it crawls through stuff", wrote one developer, while another asked whether it was "some giga expensive extra sub stuff" or worked with an existing Claude subscription ([r/aigamedev, June 18, 2026](https://www.reddit.com/r/aigamedev/comments/1u946zi/unreal_engine_58_has_al_integration_with_claude/)).

The same safety guide reminds studios that the agent subscription "is separate from Epic seat cost": the tokens are yours to budget.

### Secrets in the project

A studio project holds platform and backend credentials. The gamineai guide advises to "treat uncommitted secrets in Content or Config as exposed" and never to paste "API keys, EOS secrets, or partner URLs" into an agent that can write files.

Token-cost complaints specific to Unreal are still rare in public. The mechanics above are what drives them in every other stack: large tool results and long logs, re-read on each turn.

## What Tokenade changes for a studio

Tokenade sits between your AI agent and its tools, on each developer's computer, Windows included.

- **Large MCP results are folded.** In Claude Code, MCP results are folded after each call. For other agents, [mcp-wrap](https://tokenade.net/en/docs/mcp-wrap) routes third-party MCP servers in their config through Tokenade: results over about 25k tokens are stashed locally and replaced by a summary, and large screenshots are shrunk.
- **Build output is folded.** Tokenade recognises the format of command output, including logs and stack traces, and passes the agent the errors and the outcome instead of every progress line. The full log stays on disk; the agent retrieves any part with `tokenade expand-ref`.
- **The C++ codebase is cheaper to navigate.** `tokenade map`, `skeleton`, `query` and `semantic` let the agent locate a class or function by structure or meaning instead of reading whole source files.
- **Re-reads and repeated images are deduplicated.** An unchanged file read again, or an identical image the agent already saw, comes back as a short pointer.
- **Credentials are masked.** Keys, tokens, private keys and high-entropy strings Tokenade recognises are masked before output reaches the agent.

On the public THOL benchmark, long sessions with Tokenade cost [39% less](https://tokenade.net/en/thol) than the same sessions without it. Editor-driven sessions are long by nature. For the general case of noisy logs, see [output filtering for command logs](https://tokenade.net/en/articles/output-filtering-command-logs).

We have not published a measurement on Unreal projects specifically. `tokenade gain` and `mcp-wrap report` show what was saved on yours, per compactor and per MCP tool.

## Unreleased game, local compaction

Your game is not out yet, and its code and assets are under NDA. Compaction runs on your machines. Source code, file contents, paths, prompts and command arguments are not sent to Tokenade's servers; only usage counts go out to meter the plan, as listed in [What Tokenade sends and stores](https://tokenade.net/en/docs/privacy-telemetry).

Tokenade does not change what your agent sends to its own model provider. It masks credentials it recognises; it does not hide player data or project content. Keep the MCP server on localhost, and keep your existing rules on secrets and crash dumps.

> Drive the Unreal editor with your AI agent without letting tool results and build logs eat the session.
>
> Install: `npm install -g @tokenade/cli && tokenade install && tokenade login` — or let your agent do it: https://tokenade.net/install.md

## Setting it up

See the [install guide](https://tokenade.net/en/docs/install) for details.

1. **Install the CLI:** `npm install -g @tokenade/cli` on each developer's computer.
2. **Wire your agents:** `tokenade install` adds hooks to Claude Code, Codex, Cursor and other supported agents, and wraps the third-party MCP servers in their configs. Hooks take effect from the next agent session, so restart the one connected to the editor.
3. **Log in:** `tokenade login`, one account per developer, unlimited machines on every account. Pricing is on the [pricing page](https://tokenade.net/en/pricing).

## FAQ

### Does Tokenade work with Epic's Unreal MCP server?

In Claude Code, Tokenade folds MCP results after the call whatever the server, so the Unreal server is covered like any other. In other agents, it applies to the servers `mcp-wrap` has wrapped, and `tokenade mcp-wrap report` shows which tools it saved on. We have not published Unreal-specific measurements.

### Will folding hide the compile error I need?

The errors are what the fold keeps. If the agent needs more, the full output is stashed locally for seven days and `tokenade expand-ref` returns it, or only the lines that match a pattern.

### Does it run on Windows?

Yes. Tokenade supports Linux, macOS and Windows, and `tokenade install` wires each supported agent on all three. The [compatibility page](https://tokenade.net/en/docs/compatibility) notes the few per-system differences.

### Does our game's code leave the studio through Tokenade?

No. Compaction is local and Tokenade's servers receive usage counts only. Your agent still sends what it reads to its model provider, as it does without Tokenade.