Release Vitals: Build Size, Memory & Performance Audits (MCP)

Release Vitals gives you evidence instead of another long list of generic warnings. It reads Unity's BuildReport, identifies the assets and files included in your player build, checks package usage against scenes and prefabs, and compares each run with a saved baseline. On Android, it can also use apkanalyzer, dexdump, and aapt2 for deeper APK, dex, ABI, and resource analysis. Every finding is classified by the strength of its evidence: Artifact-proven, Build-confirmed, Likely, Unconfirmed. You can see why a finding was reported, what impact it may have, and what tradeoffs to consider. Use Release Vitals directly in the Unity Editor or run its workflows from an MCP-compatible AI client such as Claude Code, Codex, or Gemini CLI. Build Size Audit: Builds the active target after your confirmation and measures it through Unity's BuildReport. Results include total build size, major in-build assets and output files, package risks checked against scene usage, and comparison with a saved baseline. Supported build targets are Android, WebGL, Windows, macOS, and Linux. Android builds receive additional APK, dex, ABI, and resource analysis. Existing APK files can also be analyzed without creating a new build. Memory Audit: Provides guided memory captures from the Unity Editor or a supported connected player. Each capture pauses for confirmation before continuing. Findings include oversized textures, audio decompression settings, Read/Write flags, and other asset-level risks. Where possible, findings are classified by whether the asset is confirmed or likely to be included in the build. Android device capture uses adb. Performance Audit: Runs a lightweight Editor Play Mode capture and reports worst frame windows, GC pressure, frame-time evidence, and active-scene script candidates. When Release Vitals cannot prove the cause of a frame spike, it reports the cause as unattributed instead of guessing. Performance capture currently supports Editor Play Mode. Release Diagnostics and Preflight: Checks release readiness, project and player settings, installed diagnostic tools, Unity logs, bridge availability, and workflow prerequisites. Evidence can be exported for troubleshooting or support. Build Failure Investigation: Provides a guided log-and-evidence workflow when a player build fails, helping identify the failure stage and the next useful diagnostic action. Use it with or without AI: Build size, memory, performance, and diagnostic workflows are available from the Release Vitals window inside Unity. AI integration adds natural-language workflow control and concise, evidence-based summaries through MCP. It is optional. Editor-side diagnostics remain available without Node.js or an AI client. Control and Privacy: Release Vitals does not delete assets, apply optimization changes, or change project settings automatically. Workflows that create a player build or capture diagnostic data require explicit confirmation. Generated builds, reports, baselines, captures, and workflow history are stored locally in the Unity project. Release Vitals includes no telemetry and does not send project data to a Release Vitals cloud service. When you use an external AI client, that client's own service, account, and privacy terms still apply.