Custom Nodes

​

search_custom_nodes

• action:“search” — Search by keyword; query required. Returns a ranked list of packs with id, name, author, install count, and latest version. The keyword search ranks a fixed window of packs client-side, so when it matches nothing the query is also tried as an exact registry id automatically (e.g. ‘comfyui kjnodes’ → ‘comfyui-kjnodes’). Pass a returned id to action:“details” for full info, or to install_custom_node (action:“install”).
• action:“details” — Full details for ONE pack by its exact registry id: description, author, license, repository, install count, latest version, the node types it provides, and recent version changelogs. Look up the id via action:“search” first.

​

Parameters

​

Examples

{
  "tool": "search_custom_nodes",
  "arguments": {
    "action": "search",
    "query": "face detailer",
    "limit": 5
  }
}

{
  "tool": "search_custom_nodes",
  "arguments": {
    "action": "details",
    "id": "comfyui-impact-pack"
  }
}

​

install_custom_node

• action:“install” — Install a pack by registry id, git URL, or name. Local installs prefer official comfy-cli when available; remote or CLI-unavailable installs use the ComfyUI-Manager HTTP API. A ComfyUI restart may be required. Targeting the comfyui-mcp sidebar panel pack (‘comfyui-agent-panel’ / ‘comfyui-mcp-panel’) is routed through the verified install_comfyui(action:‘panel’) path (the version is re-read from disk afterwards) and is REFUSED while the panel is version-pinned.
• action:“update” — Update an installed pack, or pass id:‘all’ to update every installed pack. Local operations prefer official comfy-cli; remote operations use Manager HTTP. Targeting the sidebar panel pack is routed through the verified install_comfyui(action:‘panel’) path. While the panel is version-pinned, BOTH a direct panel target and ‘all’ are REFUSED — ‘all’ would move the pinned panel too; clear the pin with install_comfyui(action:‘panel’)(action=‘unpin’) or update other packs individually.
• action:“reinstall” — Reinstall a pack. Local operations prefer official comfy-cli; remote operations use Manager HTTP. A ComfyUI restart may be required. A panel target is routed through the verified install_comfyui(action:‘panel’) path and is REFUSED while the panel is version-pinned.
• action:“fix” — Repair a pack’s install and Python dependencies, or pass id:‘all’ to repair every pack. Local operations prefer official comfy-cli; remote single-pack repairs use Manager HTTP. REFUSES the sidebar panel pack — ‘fix’ has no verified on-disk check, so use install_comfyui(action:‘panel’) for the panel — and refuses ‘all’ while the panel is version-pinned.
• action:“uninstall” — Uninstall a pack (removes it). IRREVERSIBLE through this tool — for a cleanup audit prefer action:“disable”, which is reversible. The pack must be one ComfyUI-Manager tracks: an id that resolves nowhere is REFUSED before anything is queued (a drained queue would otherwise read exactly like a success), and a pack that is on disk but unmanaged is named so you can remove its directory yourself. After the queue drains the installed-pack list is re-read and the pack must be GONE before anything claims ‘uninstalled’. A ComfyUI restart is required to unload it fully. REFUSES the sidebar panel pack.
• action:“disable” — Disable an installed pack WITHOUT removing it — the reversible first step of a cleanup (re-enable with action:“enable”; action:“uninstall” removes a pack outright). Uses the ComfyUI-Manager HTTP API (works against remote instances) or official comfy-cli locally, and re-reads the installed-pack list afterwards so a Manager no-op is reported as NOT disabled rather than as success. A ComfyUI restart is required for the change to take effect. REFUSES the sidebar panel pack.
• action:“enable” — Re-enable a pack previously disabled with action:“disable”. Same Manager/comfy-cli mechanics and the same post-op re-read, so a Manager no-op is reported as NOT enabled rather than as success. A ComfyUI restart is required for the change to take effect. REFUSES the sidebar panel pack.
• action:“list” — List installed packs with their version and enabled/disabled state. Uses the ComfyUI-Manager HTTP API (works against remote instances); the cm-cli fallback returns names only. Read-only.
• action:“sync_deps” — Reconcile the Python dependencies of ALL installed packs through official comfy node restore-dependencies. Requires a local ComfyUI install and comfy-cli; takes no other parameters.

​

Parameters

​

Examples

{
  "tool": "install_custom_node",
  "arguments": {
    "action": "install",
    "id": "comfyui-impact-pack"
  }
}

{
  "tool": "install_custom_node",
  "arguments": {
    "action": "list"
  }
}

{
  "tool": "install_custom_node",
  "arguments": {
    "action": "fix",
    "id": "comfyui-impact-pack"
  }
}

{
  "tool": "install_custom_node",
  "arguments": {
    "action": "disable",
    "id": "comfyui-impact-pack"
  }
}

{
  "tool": "install_custom_node",
  "arguments": {
    "action": "uninstall",
    "id": "comfyui-impact-pack"
  }
}

​

node_pack

• action:“scaffold” — Generate a new pack from a template into <COMFYUI_PATH>/custom_nodes/<name>/. Writes pyproject.toml (with the [tool.comfy] PublisherId/DisplayName/Icon table the Comfy Registry requires), init.py exporting NODE_CLASS_MAPPINGS / NODE_DISPLAY_NAME_MAPPINGS, and src/nodes.py containing a runnable sample node (INPUT_TYPES/RETURN_TYPES/FUNCTION/CATEGORY), plus .comfyignore and .gitignore. Optionally emits a web/js frontend stub (wiring WEB_DIRECTORY) and a GitHub Actions publish workflow (with_ci). This is the FIRST step of the author loop: scaffold here, then restart_comfyui to load it, test it, and finally action:“publish”. Names must be a safe lowercase slug and cannot escape custom_nodes/; an existing non-empty directory is left untouched unless overwrite is true. Requires name and display_name.
• action:“verify” — Test that a pack actually LOADS in ComfyUI — the middle step of the author loop. Restarts the local ComfyUI and waits for it to become ready, then checks that the pack’s node class_types appear in /object_info. A node that fails to import (a missing dependency or a syntax error) simply never registers, so any missing class_types pinpoint a broken pack. Provide class_types explicitly, or a pack name whose init.py declares NODE_CLASS_MAPPINGS (the keys are inferred). Needs a managed local ComfyUI. Set restart:false to check the already-running server without restarting it.
• action:“publish” — Publish a local pack to the public Comfy Registry (registry.comfy.org) by running comfy node publish inside the pack directory. First validates the pack’s pyproject.toml has the required [project].name, [project].version and [tool.comfy].PublisherId (refusing the scaffold placeholder), then publishes using the API key from the REGISTRY_ACCESS_TOKEN environment variable (passed to comfy-cli via the environment, never via logged arguments). This is the LAST step of the author loop and an IRREVERSIBLE, EXTERNAL action: it creates/updates a PUBLIC registry version that this tool cannot undo. Requires comfy-cli installed and REGISTRY_ACCESS_TOKEN set. Give name (a folder under custom_nodes/) or path (an explicit pack directory).
• action:“list_files” — List the files in one installed pack under custom_nodes/<pack>/ (read-only). Skips .git/, pycache/ and node_modules/. Use this to orient before action:“read” / action:“search” when diagnosing or editing a pack you found via bisect or install_custom_node (action:“fix”). Requires pack.
• action:“read” — Read a slice of ONE file inside a pack (read-only), with bounded output so a huge file can’t flood the context. Returns the requested line range with a truncation notice when clipped; long lines are chunked. Pair with action:“search” to locate the line, then action:“patch” or action:“write” to change it. Requires path.
• action:“search” — Regex-search custom-node source under custom_nodes/ (read-only). Uses ripgrep when it’s on PATH, otherwise a bounded built-in scanner (skips dot-dirs, pycache/node_modules, binary and >1 MiB files). Returns file/line/text matches with per-line and result caps. Use this to find where a node class, import, or error string lives before reading or patching. Requires query.
• action:“write” — Create or overwrite ONE file inside a pack. Refuses to clobber an existing file unless overwrite is true, and creates parent directories by default. Use for whole-file edits or new files; for surgical edits prefer action:“patch”. After writing, run action:“verify” and restart_comfyui to load the change. Requires path and content.
• action:“patch” — Apply a unified diff to custom-node source under custom_nodes/. Every touched path is jail-checked BEFORE any git call, then the patch is validated with git apply --check and only applied if the check passes (two-phase; never uses —unsafe-paths). Paths are relative to custom_nodes/ and may carry a/ b/ prefixes; works on non-repo packs too. Ideal for surgical edits located via action:“search”. Requires patch.
• action:“git” — Run a git operation inside one pack, selected by git_action (status/diff/log/commit/push). Reads (status/diff/log) are always allowed. Writes (commit/push) require the environment flag COMFYUI_MCP_ALLOW_GIT_WRITES=1 (default OFF) and otherwise return a structured DISABLED_BY_CONFIG refusal so you can self-correct. commit requires a message and stages either the given paths or all pack changes. This is the final step of the author loop after scaffold → write/patch → verify → restart_comfyui, before action:“publish”. Requires pack and git_action.

​

Parameters

​

Examples

{
  "tool": "node_pack",
  "arguments": {
    "action": "scaffold",
    "name": "my-cool-nodes",
    "display_name": "My Cool Nodes"
  }
}

{
  "tool": "node_pack",
  "arguments": {
    "action": "search",
    "query": "class .*Sampler",
    "glob": "**/*.py"
  }
}

{
  "tool": "node_pack",
  "arguments": {
    "action": "read",
    "path": "my-cool-nodes/src/nodes.py",
    "line_count": 60
  }
}

{
  "tool": "node_pack",
  "arguments": {
    "action": "write",
    "path": "my-cool-nodes/src/nodes.py",
    "content": "# ...the full new contents of the file...",
    "overwrite": true
  }
}

{
  "tool": "node_pack",
  "arguments": {
    "action": "verify",
    "name": "my-cool-nodes"
  }
}

{
  "tool": "node_pack",
  "arguments": {
    "action": "git",
    "pack": "my-cool-nodes",
    "git_action": "commit",
    "message": "fix: sampler returns the right latent"
  }
}

{
  "tool": "node_pack",
  "arguments": {
    "action": "publish",
    "name": "my-cool-nodes"
  }
}

​

node_snapshot

• action:“list” — List the snapshots ComfyUI-Manager knows about. No other parameters. Read-only.
• action:“save” — Save the current custom-node and version state. With no name, Manager assigns a timestamped snapshot (works against remote instances). Providing name writes a custom-named snapshot file, which requires a local ComfyUI install root (COMFYUI_PATH or a saved default workspace — see the workspace tool) and is unavailable against a genuinely remote ComfyUI.
• action:“restore” — Restore a previously saved snapshot by name (required). ComfyUI-Manager applies the custom-node changes on the next ComfyUI restart; use action:“list” to find available names.

​

Parameters

​

Examples

{
  "tool": "node_snapshot",
  "arguments": {
    "action": "save",
    "name": "before-impact-pack"
  }
}

{
  "tool": "node_snapshot",
  "arguments": {
    "action": "restore",
    "name": "before-impact-pack"
  }
}

​

bisect

• action:“start” — Begin a session over all currently-enabled custom nodes. Enables half and disables the rest for the first test round, then guide the search with good/bad. Prefers the ComfyUI-Manager HTTP API; falls back to toggling .disabled directory suffixes for local installs. A ComfyUI restart may be needed for changes to take effect.
• action:“good” — Mark the currently enabled set as GOOD (the problem is absent with this set). Narrows the search to the disabled candidates and enables the next subset. Resolves and reports the culprit when one node remains.
• action:“bad” — Mark the currently enabled set as BAD (the problem is present with this set). Narrows the search to the enabled subset and enables the next subset. Resolves and reports the culprit when one node remains.
• action:“reset” — Re-enable all custom nodes and clear the session. Use to abort a bisection or restore the installation after the search completes.
• action:“status” — Report the current session state: status (idle/running/resolved), the remaining candidate node set, which nodes are enabled this round, and the identified culprit if resolved. All actions are argument-free; action is the only parameter. good/bad require a session already started with action:“start”.

​

Parameters

​

Example

{
  "tool": "bisect",
  "arguments": {
    "action": "start"
  }
}