hud analyze command inspects MCP environments to discover tools and capabilities. By default it uses cached metadata; pass --live (or Docker args) to run a container.
Usage
Arguments
Docker image to analyze (omit when using —config or —cursor)
Options
Output format:
interactive, json, or markdown. Short: -fShow input schemas in fast mode and more details in live mode. Short:
-vRun container for live analysis (slower but exact)
JSON file with MCP configuration (always live). Short:
-cAnalyze a Cursor MCP server (always live)
Analysis Modes
Fast Mode (Default)
Sources (in order):- Local HUD cache:
~/.hud/envs/<digest>/hud.lock.yaml - HUD registry metadata (if available)
- Basic Docker manifest info
Live Mode
Runs the container and queries the server:Providing Docker args (after the image) automatically switches to live mode.
Output Formats
interactive(default): rich table/tree viewsjson: structured output for toolingmarkdown: docs-friendly summaries
Examples
Tips
- Prefer fast mode during iteration; switch to
--livefor final validation. - If metadata isn’t found, the command suggests pulling or running live.