Release Vitals: Build Size, Memory & Performance Audits (MCP)
Moonlight Ember
$43.99
(no ratings)
Jump AssetStore
Evidence-first release diagnostics for Unity, driven by your AI client.YOUR UNITY BUILD IS BIGGER THAN EXPECTED. RELEASE VITALS SHOWS YOU WHAT IS ACTUALLY SHIPPING.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- UnconfirmedYou can see why a finding was reported, what impact it may have, and what tradeoffs to consider. "Probably unused" means something worth checking. It never means safe to delete automatically.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.RELEASE WORKFLOWSBuild Size AuditBuilds 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 AuditProvides 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 AuditRuns 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 PreflightChecks 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 InvestigationProvides 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 AIBuild 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 PRIVACYRelease 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.The MCP integration uses one readable JavaScript relay file and an authenticated localhost connection to Unity. It includes no node_modules directory, requires no npm install, and runs no permanent background daemon.PLATFORM SUPPORT- Tested with Android, WebGL, Windows, and macOS- Linux uses the same standalone-player build path- Android adds deep APK analysis and optional on-device memory capture- Performance capture currently runs in Editor Play Mode- iOS build-size analysis is not currently supportedREQUIREMENTS- Unity 6000.3.5f2 or newer- Unity Registry package com.unity.nuget.newtonsoft-json 3.2.2, resolved automatically from the included Package Manifest- Node.js 18 or newer for MCP and AI integration only- An MCP-compatible AI client for optional AI workflows- Unity must remain open while an AI client uses Release Vitals- Android Build Support is required for Android builds, deep APK analysis, and Android device captureTHIRD-PARTY SOFTWAREThis asset uses Unity Newtonsoft JSON through the official com.unity.nuget.newtonsoft-json package under the Unity Companion License. See Third Party Notices.md in the package for details.• Five guided release workflows — build size, memory, performance, release diagnostics & preflight, and build-failure investigation.• Evidence tiers on every finding — artifact-proven, BuildReport-confirmed, likely win, unconfirmed hygiene, or unavailable.• Build-size audit — APK category totals, top in-build assets via BuildReport, verified-unused package detection, baseline compare on every run.• Memory audit — guided Editor and connected-player captures with an explicit Play Mode capture gate.• Performance audit — worst frame windows, GC pressure, active-scene script candidates, optional ProfilerMarker attribution.• Works through any MCP stdio client (Claude Code, Codex CLI, Gemini CLI) — or fully from the in-Editor Release Doctor window.• Local-first — localhost bridge, no cloud, no telemetry, read-only by default.• One plain-JavaScript relay file — no node_modules, no native binaries, no background daemons.• Run history, baselines, and exportable evidence bundles (report.json, CSV, Markdown).• Compatible with Built-in, URP, and HDRP.





