comfyops-mcp

Overview Schema Source Related Servers Discussions Admin

comfy_nodes

Resolve missing ComfyUI custom nodes by mapping class types to Manager packages, installing them, restarting ComfyUI, and re-validating workflows.

Instructions

Install and resolve ComfyUI custom nodes via ComfyUI-Manager.

Maps missing node class_types → Manager packages (registry/GitHub catalog), installs via cm-cli or Manager REST queue, restarts ComfyUI, re-validates.

Return Format

{"success": bool, "packages": [...], "mapped": {...}, "message": str}

Examples

comfy_nodes(operation="status")
comfy_nodes(operation="ensure", workflow_id="my-complex-wf")
comfy_nodes(operation="install", packages="ComfyUI-Impact-Pack,ComfyUI-VideoHelperSuite")
comfy_nodes(operation="resolve", missing_types="ImpactInt,VHS_LoadVideo")

Input Schema

TableJSON Schema

Name	Required	Description
`git_url`	No	Git repo URL for install_git.
`packages`	No	Comma-separated Manager package names for install.
`operation`	Yes	Operation to perform.
`workflow_id`	No	Workflow ID for ensure/resolve.
`auto_install`	No	Override COMFYOPS_AUTO_INSTALL_NODES.
`missing_types`	No	Comma-separated class_types for resolve.
`workflow_json`	No	Raw workflow JSON for ensure/resolve.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 15, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden and does disclose meaningful behavior: installation via cm-cli or Manager REST queue, restart of ComfyUI, and re-validation after install. It also specifies the return format. It does not detail per-operation side effects or permission needs, but the main mutating behavior is transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, followed by a compact process line, return format, and useful examples. Every section earns its place and there is no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 7 parameters and 6 operations with no annotations. The description covers overall behavior and some examples, but leaves the mappings and install_git operations underspecified and does not clearly distinguish 'ensure' from 'resolve'. An agent could still be uncertain which operation to invoke in edge cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by showing concrete operation-to-parameter examples (install→packages, resolve→missing_tpes, ensure→workflow_id) and explaining the mapping concept from missing class_types to packages.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource+mechanism: 'Install and resolve ComfyUI custom nodes via ComfyUI-Manager.' The mapping of missing class_types to packages and the examples distinguish it from sibling tools focused on generation, workflows, models, or library management.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear context is given: the tool maps missing node class_types to Manager packages, installs, restarts, and re-validates. This implies when to use it (missing/required custom nodes), though it does not explicitly name alternatives or state when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server