XUUnity MCP is strongest when the AI workflow has to prove project health, not just mutate editor state.
Run player script compile validation without switching the active build target, including matrix-style checks across targets and defines.
Execute tests with normalized result accounting while keeping Test Framework optional rather than a hard dependency.
Use scene snapshots and assertions when an agent needs proof of scene state instead of loose narrative summaries.
Use console tail and status summary commands to tighten feedback loops after edits, imports, or package changes.
Capture screenshots for verification-oriented agent loops after capability probing confirms support.
Replay bounded scenarios with persisted result payloads for deterministic validation and recovery-aware follow-ups.
| Workflow stage | Recommended action |
|---|---|
| Before mutation | Run setup-plan and review the proposed file/config changes. |
| After approval | Run setup-apply, then validate-setup. |
| When Unity may not be ready | Run ensure-ready before the first status or test command. |
| First live probe | Use request-status-summary or unity_status_summary depending on client reload state. |
| Validation phase | Run compile checks, tests, scene assertions, and screenshots as needed. |