installer-packs

1# Installer Packs
2 
3`comfyui-mcp` ships **installer packs** under [`packs/`](../../packs). Each pack
4is a one-command setup for a model family: custom nodes, model weights, and a
5ready workflow. A single `manifest.yaml` (a `ComfyManifest`, the same shape the
6`apply_manifest` tool consumes) drives both the MCP-native install and the
7generated double-click scripts.
8 
9```
10packs/<name>/
11  manifest.yaml         # custom_nodes + models (url → local_path) — source of truth
12  pack.yaml             # metadata: workflow, family, VRAM, sources, notes
13  workflow.json         # the graph to load
14  install-windows.bat   # GENERATED — never hand-edit
15  install-runpod.sh     # GENERATED — never hand-edit
16```
17 
18## Installing a pack
19 
20- **From a Claude session (MCP-native, idempotent):**
21  `apply_manifest --path packs/<name>/manifest.yaml` (requires `COMFYUI_PATH`).
22  It installs the custom nodes and downloads the models, skipping anything
23  already present.
24- **One-click for non-MCP users:** run `packs/<name>/install-windows.bat` (or
25  `install-runpod.sh`) from a ComfyUI root. Then load the pack's `workflow.json`.
26- After install, check the pack's `pack.yaml` `notes`/`post_install` for
27  model-specific gotchas (VRAM tiers, SageAttention/Triton, dtype fixes, etc.).
28 
29## Building or deriving a new pack
30 
31Two sources of ground truth, in order of preference:
32 
331. **An upstream installer** (`*-MODELS-NODES_INSTALL.bat` / `.sh`). Parse its
34…