Skip to content

UVCS MCP 1.2.0

Choose a tag to compare

@Feargin Feargin released this 23 Jul 19:04
· 13 commits to main since this release

UVCS MCP 1.2.0

UVCS MCP 1.2.0 makes safe agent-assisted source-control work practical across both one project and fleets of Plastic SCM / Unity Version Control workspaces.

Highlights

  • One MCP process can serve up to 50 named workspaces from a fleet manifest.
  • Every fleet tool call uses an explicit workspace selector.
  • Workspace policies, repository allowlists, confirmation tokens, audit logs, and write locks remain isolated.
  • readonly, guarded, and standard safety profiles make setup intent explicit.
  • uvcs-mcp doctor --manifest=... validates every configured workspace before client restart.
  • Guarded setup can detect repository/server identity from real Plastic workspace status.
  • Naming, checkin, and release rules can be initialized per workspace or inherited from a shared policy.
  • Path-scoped uvcs_undo_prepare / uvcs_undo_confirm adds controlled undo without exposing whole-workspace undo.

Reliability and security

  • Confirmation tokens are short-lived, single-use, action-scoped, and workspace-bound.
  • Switch, merge, update, undo, and checkin revalidate workspace state after prepare.
  • Writes are serialized across requests and MCP processes.
  • Workspace paths are canonicalized and protected against escape.
  • Read and write timeouts are separate, and process output is bounded.
  • Runtime dependencies are pinned and production audits are enforced in CI and publishing.
  • Codex TOML setup safely replaces an existing MCP server and descendant environment tables.

Setup

One workspace:

npx -y @proanima/uvcs-mcp@1.2.0 init \
  --client=cursor,codex \
  --workspace="D:/Repositories/YourWorkspace" \
  --safety=guarded

npx -y @proanima/uvcs-mcp@1.2.0 doctor \
  --workspace="D:/Repositories/YourWorkspace"

Multiple workspaces:

npx -y @proanima/uvcs-mcp@1.2.0 init \
  --client=cursor,codex \
  --manifest=workspaces.json

npx -y @proanima/uvcs-mcp@1.2.0 doctor \
  --manifest=workspaces.json

Validation

  • 70 automated tests.
  • Full single-workspace MCP smoke workflow.
  • Parallel two-workspace fleet smoke with independent naming rules and branches.
  • Dependency audits with zero known vulnerabilities.
  • npm package dry run.
  • Read-only live validation on Plastic SCM 10.0.16.6656.

Upgrade notes

  • Existing single-workspace configurations remain supported.
  • Fleet mode is opt-in through UVCS_FLEET_MANIFEST.
  • Existing standard configurations continue to work; guarded is recommended for production writes.
  • Restart the MCP client after upgrading.

See the multi-workspace guide, security model, and production-readiness checklist for operational details.