v2.15.0 — Multi-Instance Support

What's New

v2.15.0 — Multi-Instance Support

Run multiple Unity Editor instances simultaneously, each on its own port. Designed for working on several projects at once or multiplayer development with ParrelSync clones.

New: MCPInstanceRegistry System

• Auto-port selection — Each Unity instance picks the first available port from 7890–7899 on startup. No manual configuration needed.
• Shared instance registry — Every running instance writes its metadata (port, project name, path, PID, Unity version) to %LOCALAPPDATA%/UnityMCP/instances.json (macOS: ~/Library/Application Support/UnityMCP/instances.json).
• Automatic cleanup — Instances unregister on stop, quit, or domain reload. Stale entries from crashed processes are cleaned up on next startup.
• ParrelSync clone detection — Clones are automatically detected and labeled throughout the UI.

Dashboard & Toolbar Updates

• Connection status shows active port with auto/manual indicator
• ParrelSync clone indicator displayed below status bar (e.g. "ParrelSync Clone #0")
• New Use Manual Port toggle in Settings — override auto-selection when needed
• Toolbar tooltip and dropdown show port, mode, and clone info
• Settings reorganized into submenu (Auto-Start + Use Manual Port)

How It Works

                                                  ┌─ Unity Instance A (port 7890)
Claude Cowork Agents ←→ MCP Server (Node.js) ←→───┤
       ↕                       ↕                   └─ Unity Instance B (port 7891)
  Multiple agents        Unity Hub CLI                        ↕
  working in parallel                              Shared Instance Registry

Compatibility

• Fully backward compatible — single-instance setups work exactly as before
• Requires server v2.15.0+