Date: 2026-05-23
Status: current for v0.3.17
XUUnity is the surrounding AI-assisted Unity workflow system used by this project. The MCP service can also be consumed as a standalone Unity Editor automation layer.
MCP means Model Context Protocol. It lets AI clients call structured tools exposed by a local or remote server.
The host-side server is the local process that speaks MCP to AI clients and routes requests to a Unity project.
The Unity package is com.xuunity.light-mcp. It contains the editor-side bridge and editor-only operations used by the host-side MCP server.
Current production Git UPM path:
https://github.com/FoxsterDev/xuunity-light-unity-mcp.git?path=/packages/com.xuunity.light-mcp#v0.3.17
Git UPM is Unity Package Manager installing a package directly from a Git URL. It is the current production install route for this package until OpenUPM is published.
OpenUPM is a public Unity package registry. XUUnity Light Unity MCP has a registry-native package path, but the documented install route is still Git UPM until an OpenUPM package page exists.
devmode points a consumer Unity project at the local package folder for MCP
package development.
prodmode points a consumer Unity project at a published Git package source.
It pins the package to the published release tag that matches the package
version so release-bound projects do not depend on local-only package changes.
An MCP feature that may be supported, unsupported,
disabled_missing_dependency, disabled_dependency_too_old, degraded, or
error without making the core MCP health fail.
The optional EditMode and PlayMode test surface backed by
com.unity.test-framework. Unity enables it through asmdef Version Defines
when XUUNITY_LIGHT_MCP_TESTS_CAPABILITY is available.
BridgeRegistry is the local routing layer used to map MCP requests to the correct Unity project/editor instance on the same host.
ProjectContext is the host-side state for a single Unity project, including project paths, bridge state, editor session evidence, and request routing metadata.
Same-host automation means the AI client, MCP server, and Unity Editor run on the same trusted machine or CI host.
The request journal is the per-project record under
Library/XUUnityLightMcp/journal/requests/ used to recover final request status
after Unity reloads, transport churn, or wrapper timeouts.
A scenario is a bounded JSON workflow that asks Unity MCP to perform ordered validation steps such as refresh, compile, Play Mode, scene checks, screenshots, or project-defined hooks.