Unity Devloop MCP
Provides tools for interacting with the Unity Editor's edit → compile → check loop: reading editor status (project path, Unity version, active scene, build target, compiling/playing/paused state), retrieving console entries including compiler errors and warnings with stack traces, triggering AssetDatabase.Refresh to import external file changes and start recompilation, and executing editor menu items by path. Works via a local-only editor bridge that runs requests on the main thread.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Unity Devloop MCP refresh the assets and show me any compile errors"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
unity-devloop-mcp
MCP server for the Unity edit → compile → check loop. An AI client (Claude Code, etc.) can read the editor state and console/compiler errors, trigger an asset refresh after editing scripts outside Unity, and run menu items — without you copying console output by hand.
Two parts:
Part | Path | Role |
MCP server (Node, stdio) |
| Exposes the tools below and forwards calls to the editor |
Unity bridge (UPM, Editor-only) |
| Local HTTP listener on |
The bridge listens only on 127.0.0.1 and only while the editor is open. Nothing is included in player builds.
Tools
Tool | Input | Result |
| — | project path, Unity version, active scene, build target, |
|
| recent entries captured by the bridge (stack traces kept for errors/exceptions) |
| — | runs |
|
| runs |
Console capture starts when the bridge loads, so entries from before the last script reload are not kept. Compiler errors are captured from CompilationPipeline and survive a failed compile (no reload happens on failure).
Related MCP server: ach-mcp
Install
1. Unity package
Add to Packages/manifest.json:
"com.shin0112.unity-devloop-mcp": "https://github.com/shin0112/unity-devloop-mcp.git?path=/unity-package"or, for a local clone:
"com.shin0112.unity-devloop-mcp": "file:C:/projects/unity-devloop-mcp/unity-package"Menu: Tools > Unity Devloop MCP > Status / Enable Bridge / Disable Bridge.
2. MCP server (Claude Code)
From GitHub:
claude mcp add unity-devloop -- npx -y github:shin0112/unity-devloop-mcpFrom a local clone:
cd C:/projects/unity-devloop-mcp && npm install
claude mcp add unity-devloop -- node C:/projects/unity-devloop-mcp/server/index.jsConfiguration
Setting | Where | Default |
Port | EditorPrefs |
|
Request timeout | env |
|
Notes
Requests run on the editor main thread via
EditorApplication.update. If the editor is unfocused and throttles updates, calls may be slow or time out.During a script reload the bridge restarts; calls fail briefly with "not reachable".
unity_execute_menucan run any menu item. Only connect clients you trust.
License
MIT
Available Tools
4 toolsunity_consoleB
Recent Unity console entries captured by the bridge (logs, warnings, errors, exceptions, compiler messages). Entries before the last script reload are not kept.
Inputs: clear, limit, types.
unity_refreshA
Run AssetDatabase.Refresh so file changes made outside the editor are imported and scripts recompile.
Inputs: no named parameters.
unity_statusB
Editor state: project path, Unity version, compiling, play mode, active scene, build target.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool targets a clearly distinct concern: reading editor state, reading console output, executing a menu action, and refreshing assets. There is no realistic confusion between them, as names and descriptions point to different resources and actions.
All tools share a consistent 'unity_' prefix, but the remainder mixes nouns (status, console) with verb phrases (execute_menu, refresh). It is still highly readable and predictable overall.
Four tools is a focused, reasonable scope for a lightweight editor bridge, though it sits at the thin end and could plausibly include one or two more operations (e.g., play mode control, test running).
The core dev loop is covered: inspect state, read console diagnostics, refresh/import external changes, and run arbitrary menu items as an escape hatch. Direct play mode toggle or test execution would round it out, but the menu escape hatch mitigates most gaps.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to control Unreal E…
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Make games with AI: one MCP server that connects your agent to Unity, Unreal and Godot editors.
Control Unreal Engine to browse assets, import content, and manage levels and sequences. Automate…
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceUnity Editor automation bridge for AI agents and MCP clients, enabling inspection, control, and diagnostics of the Editor.MIT
- FlicenseNot gradedqualityDmaintenanceAn in-editor MCP server that exposes Unity convenience tools to AI assistants, allowing them to read console logs, execute menu items, dump scene hierarchies, and take screenshots.-
- FlicenseNot gradedqualityDmaintenanceLocal Streamable HTTP MCP server exposing Unity Editor inspection, authoring, testing, profiling, play-mode, and build tools.-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to drive the Unity Editor directly over HTTP, including scene and asset editing, diagnostics, play mode control, code execution, input simulation, and builds, with no separate MCP server process.344MIT