UVCS MCP — Claude Code MCP server: what it does, how to install
UVCS MCP connects AI assistants to Plastic SCM and Unity Version Control via the cm CLI. Enables repository inspection, branch setup, and guarded checkins.
MIT ★ 18 updated 2026-10-26
claude mcp add --env UVCS_WORKSPACE=<UVCS_WORKSPACE> --env UVCS_MCP_MODE=<UVCS_MCP_MODE> --env UVCS_ALLOWED_WORKSPACES=<UVCS_ALLOWED_WORKSPACES> --env UVCS_ALLOWED_REPOS=<UVCS_ALLOWED_REPOS> --env UVCS_CM_PATH=<UVCS_CM_PATH> --transport stdio uvcs-mcp -- npx -y @proanima/uvcs-mcpWhat UVCS MCP does
The server exposes Plastic SCM, Unity Version Control, and Unity DevOps Version Control workspaces to AI agents via the cm command-line tool. It supports client versions 10.0.16.6656 and newer, including 11.x releases. Agents can review status diffs, inspect incoming changes, build branches, assign labels, and run merges without unrestricted terminal access.
It is not a Unity Editor automation bridge. The tool does not touch GameObjects, scenes, active Play Mode, or package windows; its scope remains strictly inside source control. The default operational profile is readonly. Modifications need standard mode and use a two-phase prepare-and-confirm sequence. During partial checkins, it automatically detects .meta companion files and stops if a meta file remains untracked.
The server fails immediately if Node.js is older than version 22 or if the local cm CLI is not authenticated.
What it helps with
- inspect Plastic SCM workspace state and pending changes
- commit Unity assets while ensuring matching
.metafiles are included - create branches and tags without granting arbitrary terminal execution
- preview incoming merges and abort when merge conflicts exist
Example prompts for the agent
- Check the Unity Version Control workspace status and list pending changes
- Prepare a checkin for modified assets along with their corresponding meta files
- Run a merge preview from the target branch and check for unresolved conflicts
How to install UVCS MCP
Platform CLI
claude mcp add --env UVCS_WORKSPACE=<UVCS_WORKSPACE> --env UVCS_MCP_MODE=<UVCS_MCP_MODE> --env UVCS_ALLOWED_WORKSPACES=<UVCS_ALLOWED_WORKSPACES> --env UVCS_ALLOWED_REPOS=<UVCS_ALLOWED_REPOS> --env UVCS_CM_PATH=<UVCS_CM_PATH> --transport stdio uvcs-mcp -- npx -y @proanima/uvcs-mcpReplace <…> with your own values
Platform CLI
codex mcp add uvcs-mcp --env UVCS_WORKSPACE=<UVCS_WORKSPACE> --env UVCS_MCP_MODE=<UVCS_MCP_MODE> --env UVCS_ALLOWED_WORKSPACES=<UVCS_ALLOWED_WORKSPACES> --env UVCS_ALLOWED_REPOS=<UVCS_ALLOWED_REPOS> --env UVCS_CM_PATH=<UVCS_CM_PATH> -- npx -y @proanima/uvcs-mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"uvcs-mcp": {
"command": "npx",
"args": [
"-y",
"@proanima/uvcs-mcp"
],
"env": {
"UVCS_WORKSPACE": "<UVCS_WORKSPACE>",
"UVCS_MCP_MODE": "<UVCS_MCP_MODE>",
"UVCS_ALLOWED_WORKSPACES": "<UVCS_ALLOWED_WORKSPACES>",
"UVCS_ALLOWED_REPOS": "<UVCS_ALLOWED_REPOS>",
"UVCS_CM_PATH": "<UVCS_CM_PATH>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"uvcs-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@proanima/uvcs-mcp"
],
"env": {
"UVCS_WORKSPACE": "<UVCS_WORKSPACE>",
"UVCS_MCP_MODE": "<UVCS_MCP_MODE>",
"UVCS_ALLOWED_WORKSPACES": "<UVCS_ALLOWED_WORKSPACES>",
"UVCS_ALLOWED_REPOS": "<UVCS_ALLOWED_REPOS>",
"UVCS_CM_PATH": "<UVCS_CM_PATH>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e UVCS_WORKSPACE=<UVCS_WORKSPACE> -e UVCS_MCP_MODE=<UVCS_MCP_MODE> -e UVCS_ALLOWED_WORKSPACES=<UVCS_ALLOWED_WORKSPACES> -e UVCS_ALLOWED_REPOS=<UVCS_ALLOWED_REPOS> -e UVCS_CM_PATH=<UVCS_CM_PATH> uvcs-mcp npx -y @proanima/uvcs-mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about UVCS MCP
How to install UVCS MCP in Claude Code?
Run claude mcp add uvcs-mcp -e UVCS_WORKSPACE=<UVCS_WORKSPACE> -- npx -y @proanima/uvcs-mcp with the path to your source-control workspace.
Does UVCS MCP automate Unity Editor actions?
No, it interfaces strictly with the Plastic SCM cm tool. It does not inspect scenes, manipulate packages, or trigger Play Mode inside the engine.
What dependencies does UVCS MCP require?
It requires Node.js 22 or higher, an existing workspace folder, and an authenticated cm CLI version 10.0.16.6656 or newer.