Unity MCP Efficient
A small compatibility layer that lets AI clients use MCP for Unity without loading its full tool surface into every prompt.
The model sees six stable tools and discovers the required Unity operation on demand. The facade then compacts routine output, preserves full results for bounded retrieval, and batches related work without forcing every intermediate response into the conversation.
Measured against MCP for Unity v10.1.0, the model-visible schema fell from 23,280 estimated tokens to 915, while 377 indexed Unity operations remained reachable. The reproducible benchmark measures context footprint, not API billing.
[!IMPORTANT] This project does not replace the Unity package or its Python server. MCP for Unity remains the backend. Register the facade, not the upstream server, with the AI client. Exposing both tool surfaces removes most of the context savings.
Measured context reduction
On 2026-08-24, the scripts in benchmarks/ produced these results against MCP for Unity v10.1.0 (c14de1e6).
The dynamic catalog indexed 377 Unity operations. A small deterministic English/Russian search suite returned the expected operation at rank 1 for all 15 cases and within the top 3 for all 15 cases. The release candidate passes 35 facade tests. A live smoke test made no project changes and verified the six-tool surface, editor.refresh at rank 1, editor state, and a two-step scene inspection batch against an open Unity Editor.
¹ Token counts use a transparent four-characters-per-token estimate. They describe context footprint, not API billing. Actual tokenization varies by model and payload.
² The hierarchy benchmark models a noisy response containing 250 objects, 300 vertex indices per object, and the same data in text and structured payloads. This stress case does not promise the same reduction for every scene. See BENCHMARKS.md for the method and raw values.
What the six tools do
The model still reaches the 377 indexed operations behind the facade. Those operations no longer occupy the prompt all at once.
Problems handled at the boundary
Architecture
Codex or another MCP client
|
| sees 6 tools
v
Unity MCP Efficient (stdio by default)
|-- capability search over the live upstream catalog
|-- compact Unity-specific post-processing
|-- bounded workflow runtime
|-- local SQLite result and request receipts
|
| HTTP, default http://127.0.0.1:8080/mcp
v
MCP for Unity server
|
v
Unity Editor package
A skill alone cannot hide tool schemas that an MCP client has already loaded. That is why this repository contains both pieces:
- the facade enforces the smaller API and compact responses;
- the skill teaches Codex how to search, batch, recover, and verify efficiently.
Install
1. Start MCP for Unity in HTTP mode
Install CoplayDev/MCP for Unity using its upstream instructions. In Unity, open Window → MCP for Unity, select the local HTTP transport, and start the server.
The upstream default endpoint is:
http://127.0.0.1:8080/mcp
If your project uses another port, pass it through UNITY_MCP_BACKEND_URL below.
2. Register the facade in Codex
Install uv when needed, then run:
codex mcp add unity-efficient \
--env UNITY_MCP_BACKEND_URL=http://127.0.0.1:8080/mcp \
-- uvx --from git+https://github.com/Vangardo/[email protected] unity-mcp-efficient
On PowerShell, use the same command on one line:
codex mcp add unity-efficient --env UNITY_MCP_BACKEND_URL=http://127.0.0.1:8080/mcp -- uvx --from git+https://github.com/Vangardo/[email protected] unity-mcp-efficient
Remove or disable any direct MCP for Unity entry from the same Codex client. Keep the upstream HTTP server running, but do not register its 48-tool surface with the model.
3. Install the Codex skill
The easiest route is to ask Codex:
$skill-installer Install the skill from https://github.com/Vangardo/unity-mcp-efficient/tree/v0.2.0/skills/unity-mcp-efficient
For a manual user-level install, clone the repository and copy skills/unity-mcp-efficient to:
$HOME/.agents/skills/unity-mcp-efficient
Codex detects skill changes automatically. Restart it if the skill does not appear.
Other MCP clients
Use this stdio configuration shape:
{
"mcpServers": {
"unity-efficient": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/Vangardo/[email protected]",
"unity-mcp-efficient"
],
"env": {
"UNITY_MCP_BACKEND_URL": "http://127.0.0.1:8080/mcp"
}
}
}
}
Install the packaged skill when the client supports the Agent Skills format. The facade works without it, but the skill improves tool selection and recovery behavior.
Recommended agent loop
- Inspect low-detail Unity state once.
- Search with one concrete task phrase.
- Request the selected schema when its arguments are unclear.
- Batch known dependent work sequentially. Parallelize independent reads, never Unity mutations.
- Keep compact output and expand stored results by path or page.
- Verify the semantic result, not every raw intermediate object.
This loop is already encoded in skills/unity-mcp-efficient/SKILL.md.
Configuration
Keep the default stdio transport unless you have a reason to expose the facade over a network. Read SECURITY.md before using HTTP or SSE.
Development and verification
git clone https://github.com/Vangardo/unity-mcp-efficient.git
cd unity-mcp-efficient
uv sync --extra dev
uv run pytest -q
With the upstream HTTP server running:
uv run python benchmarks/evaluate_facade.py
uv run python benchmarks/measure_surface.py
uv run python benchmarks/live_smoke.py
evaluate_facade.py and measure_surface.py read the live upstream catalog. live_smoke.py makes no mutations, but it requires an open and connected Unity Editor.
Known boundaries
- Compact output is intentionally lossy. The untouched raw result remains available through
get_resultfor a bounded time. - The facade does not make arbitrary Unity mutations safe. Permissions and review still belong to the MCP client and user.
- Parallel mode is conservative. Unity may serialize editor work internally.
- A discoverable optional capability, such as Roslyn support, may still be absent from a particular Unity project.
- Scene and Game view capture may omit IMGUI or editor overlays.
- Compatibility tests use MCP for Unity
v10.1.0. The catalog is dynamic; benchmark later upstream releases before claiming support.
Design lineage
We took the progressive-disclosure idea from work on Vangardo/mcp_hub, a broader MCP gateway that routes a large integration catalog through a small search-and-call surface. Unity MCP Efficient applies that context discipline to Unity, then adds Unity-specific compaction, revision checks, mutation recovery, screenshots, and bounded local workflows.
If you need this pattern for Slack, Teamwork, Telegram, calendar, memory, automation, or cross-service agents, see MCP Hub.
The Unity compatibility backend is CoplayDev/MCP for Unity, distributed under the MIT License. This repository is an independent project and does not include its source code. See NOTICE.md and THIRD_PARTY_NOTICES.md.
Project documents
License and trademarks
The original code in this repository is available under the MIT License.
Unity is a trademark or registered trademark of Unity Technologies or its affiliates in the United States and elsewhere. This project is not affiliated with or endorsed by Unity Technologies or CoplayDev. Other names and brands belong to their respective owners.
