comfyui-workflow

ComfyUI Workflow

Operate the user's live ComfyUI installation through the comfyui_* MCP tools. Treat the live node schema and model inventory as authoritative; installations differ because custom nodes, models, and ComfyUI versions differ.

Establish the task

1. Determine whether the user wants inspection, graph construction, graph editing, canvas display, execution, or troubleshooting.
2. Call comfyui_health before work that depends on a live ComfyUI instance.
3. Inspect managed workflows with comfyui_list_workflows and comfyui_get_workflow before assuming a workflow is absent or current.
4. Preserve the user's existing workflow unless they explicitly request replacement. Prefer a new managed workflow for experiments.

If the host prefixes MCP names, select tools by their comfyui_* suffix.

Discover before building

Never invent node class names, input names, output indices, enum values, or model filenames.

1. Search with comfyui_list_node_types using a functional term such as checkpoint, sampler, controlnet, or save image.
2. Call comfyui_get_node_type for every class whose inputs or outputs affect the graph.
3. Call comfyui_list_models before choosing checkpoints, VAEs, LoRAs, ControlNets, upscale models, or other installed assets.
4. Use comfyui_list_templates when an installed node pack may already provide a suitable workflow.

Read graph-contract.md before creating or modifying a graph.

Build or edit incrementally

1. Create an empty graph with comfyui_create_workflow, or import an API-format graph with comfyui_import_workflow.
2. Add one node at a time with comfyui_add_node. Keep verify_node_type=true unless the user is deliberately preparing a graph for a node that is not installed locally.
3. Set literals with comfyui_set_input and links with comfyui_connect_nodes.
4. After every mutation, carry the returned revision into the next mutation as expected_revision. If a revision conflict occurs, read the workflow again and reconcile instead of blindly retrying.
5. Use comfyui_disconnect_input before replacing a connection when that makes the intent clearer. Use comfyui_remove_node with force=true only when dangling connections should also be removed.
6. Keep stable node IDs and useful _meta.title values so later edits and run overrides are unambiguous.