Skip to main content
This is a Comfy Cloud feature and is only available in the cloud version. To learn more about Comfy Cloud, see Comfy Cloud.
Public beta. Comfy Cloud MCP is in public beta. APIs, tools, and behavior may change while we iterate. See Feedback to report issues or share suggestions.

Overview

The Comfy Cloud MCP server connects AI agents to Comfy Cloud over the Model Context Protocol. Once connected, you can generate images, video, audio, and 3D, search models, nodes, and templates, and run ComfyUI workflows from a chat with your agent. The server runs remotely at cloud.comfy.org/mcp. Workflows execute on Comfy Cloud GPUs, so you do not need a local GPU. Your agent talks to the server over HTTPS; the server translates tool calls into authenticated requests to Comfy Cloud on your behalf. Any MCP-compatible client can connect to the same server URL. Claude Code, Claude Desktop, Cursor, and Codex have first-class setup below. Windsurf, Amp, and other agents use the same URL with OAuth or an API key.

Install Comfy Cloud MCP

You need a Comfy Cloud account before connecting. Sign up if you do not have one yet. OAuth sign-in during setup uses your Comfy account.
Comfy Cloud MCP runs at:
https://cloud.comfy.org/mcp
Pick your client:
Install the comfy-cloud plugin. It adds the MCP connection and slash commands in one step. The plugin is published through the Comfy Skills repository, which hosts Claude Code plugins and community agent skills for Comfy.
1

Add the marketplace

Register the Comfy Skills marketplace (one-time):
/plugin marketplace add Comfy-Org/comfy-skills
2

Install the plugin

/plugin install comfy-cloud@comfy-skills
3

Sign in

Run /mcp, select comfy-cloudAuthenticate. Your browser opens to sign in, and tokens refresh automatically.
The plugin adds these slash commands:
CommandWhat it does
/comfy-cloud:generate-imageGenerate, edit, or modify an image
/comfy-cloud:generate-videoGenerate, edit, or extend a video
/comfy-cloud:generate-audioGenerate audio, music, or sound effects
/comfy-cloud:generate-3dGenerate a 3D model from text or an image
/comfy-cloud:remove-backgroundRemove the background from an image
/comfy-cloud:upscale-imageUpscale an image to higher resolution
/comfy-cloud:search-templatesFind pre-built workflow templates on comfy.org
/comfy-cloud:search-modelsSearch for available models
/comfy-cloud:search-nodesSearch for nodes and get wiring suggestions
/comfy-cloud:helpSee what you can do with ComfyUI Cloud
Add the server directly:
claude mcp add --transport http comfy-cloud https://cloud.comfy.org/mcp
Then run /mcp, select comfy-cloudAuthenticate. Add -s user to make it available in all your projects.This path still exposes the same workflows as MCP prompts: /mcp__comfy-cloud__generate-image, /mcp__comfy-cloud__search-models, and so on (the /mcp__<name>__ prefix uses the name you passed to claude mcp add). The plugin above is recommended because it wraps these as the friendlier /comfy-cloud:* commands.

What your agent can do

You do not call MCP tools yourself. Your agent picks the right tool based on what you ask for. Slash commands and prompts (below) are shortcuts that steer the agent toward common tasks, but plain language works too (“generate an image of a cat astronaut”, “upscale this photo”, “find a Wan 2.2 video template”). Typical flow:
  1. Discover what is available (search_templates, search_models, search_nodes, or cql for graph-style questions).
  2. Run a generation: run_template for a matching pre-built template, submit_workflow for a custom workflow (with upload_file when an input image is needed), or partner_generate for partner models like Flux, Grok, Gemini, OpenAI, Ideogram, and Seedance.
  3. Wait and retrieve outputs (wait_for_job, then get_output returns a download command your agent runs in your shell).
The server prefers matching pre-built templates before building a workflow from scratch, which tends to produce better results faster.

MCP tools

These are the tools your agent has access to once connected. Names match what appears in MCP client logs and debugging.

Discovery

ToolDescription
search_templatesSearch pre-built workflow templates from comfy.org by text, tag, media type, or model
get_templateFetch a template’s full workflow JSON for inspection or hand-editing
get_template_schemaSee which of a template’s parameters can be overridden at run time
search_modelsSearch the model catalog by text, type, base model, or source
search_nodesSearch available nodes by text, category, or input/output types. Also surfaces subgraph blueprints (pre-wired node groups like Text to Image or Remove Background)
get_nodeGet the complete input spec for specific nodes, including full option lists
cqlRun a CQL graph query for structural questions (for example, which nodes produce images, or paths between node types). Use search_nodes when you need full input specs for a specific node
get_prompting_guidePrompt style and recommended settings (steps, cfg, sampler, resolution) per model family

Generation

ToolDescription
run_templateRun a pre-built template by name, with optional parameter overrides — the preferred path when a template matches
submit_workflowSubmit a ComfyUI API-format workflow for execution on Comfy Cloud
partner_generateGenerate with partner-API models (Flux/BFL, Grok, Gemini, OpenAI, Ideogram, Seedream/Seedance, and more)
upload_fileUpload an input image or file for use in workflows (for example, with LoadImage)
apply_slotsApply parameter overrides to a workflow’s interior values and return the modified workflow

Jobs and batches

ToolDescription
get_job_statusPoll execution status of a submitted workflow
wait_for_jobWait until a job finishes instead of polling repeatedly
get_outputRetrieve output images, videos, or audio from a completed workflow
use_previous_outputChain workflows by reusing output from one run as input to another
cancel_jobCancel a pending or running job
get_queueCheck how many jobs are running and pending
submit_batch, get_batch_status, get_batch_output, wait_for_batchSubmit many generations in one call and collect them together later — the batch ID stays valid across sessions

Saved workflows

ToolDescription
list_saved_workflowsBrowse your saved workflows from Comfy Cloud
get_saved_workflowInspect a saved workflow’s nodes, inputs, and customizable settings
save_workflowSave a workflow to your Comfy Cloud account
update_workflowUpdate an existing workflow in place as a new version (earlier versions stay recoverable)
run_saved_workflowRun a saved workflow by filename — the server converts it from editor format to executable format automatically

Sharing workflows

ToolDescription
share_workflowPublish a saved workflow and return a ?share=<id> URL anyone can open
import_shared_workflowResolve a share URL or bare share ID into workflow JSON, optionally saving it to your account
Hub URL share IDs: the trailing hyphen-delimited hex token in a comfy.org/workflows/<slug>-<hex> hub URL is the share ID. For example, comfy.org/workflows/topaz-starlight-upscale-1c77e82713b7 has share ID 1c77e82713b7. Pass that token to import_shared_workflow as share_id. The share_url parameter only accepts ?share=<id> query URLs like https://cloud.comfy.org/?share=..., not hub page URLs.
ToolDescription
create_appTurn a saved workflow into an App Mode app — a simplified “run this workflow” view with chosen inputs and outputs
get_app_mode_urlGet the stable link that opens a workflow as a runnable app
get_workflow_canvas_urlGet a link that opens a workflow directly on the Comfy Cloud canvas, ready to view, edit, or run

Account and session

ToolDescription
get_billing_statusCheck your credit balance, subscription tier, and billing link
get_server_infoConfirm which server the agent reached: environment, host, version, and auth state
submit_feedbackGet the beta feedback survey link
report_session_summaryShare an anonymized session summary with the Comfy team — only with your explicit consent; the agent must ask first, and no prompts, file paths, or personal information are included

Credits and spending

Discovery is free: search_templates, search_models, and search_nodes work with just a Comfy account. Running generations consumes Comfy Cloud credits and requires a subscription or credit balance. Tools that spend real money are spend-gated. When a generation uses a paid partner model (partner_generate) or a workflow/template containing paid API nodes (run_template, run_saved_workflow, submit_batch), the server blocks execution until your agent confirms you agreed to spend credits — so expect the agent to check with you before those runs. Free, local-only workflows never prompt. You can ask your agent about your balance at any time (“how many credits do I have?”) — it answers via get_billing_status.

Outputs and downloads

The MCP server runs in the cloud and never writes files to your machine. When a generation completes, your agent calls get_output, which returns:
  1. A temporary signed download URL (valid for a short window).
  2. A ready-to-run shell command (curl on macOS and Linux, curl.exe on Windows).
Your agent should run that command in your shell. The command includes the destination path and filename.
Run the returned command verbatim. Do not re-encode or edit the signed URL. The signature lives in the query string and breaks if the URL is modified.
If your MCP client cannot run shell commands (some GUI-only setups), copy the command and run it yourself in a terminal.
ResourceWhat it’s for
Comfy SkillsClaude Code plugin marketplace and community skill library. The comfy-cloud plugin used above is distributed here; browse or contribute additional skills for Comfy workflows.
Comfy CLICommand-line tool for local ComfyUI install/launch and for calling hosted partner nodes from scripts or CI (comfy generate, in beta). Complements MCP when you need terminal or automation workflows.
Share a workflow on Comfy CloudShare workflows from the Comfy Cloud UI (the MCP share_workflow tool does this from an agent session).

Feedback

Comfy Cloud MCP is in public beta. Please try it out and tell us what works and what doesn’t:

Known limitations

Comfy Cloud MCP is an early release. These limitations are known and being worked on: Workflows
  • Editor-to-executable conversion has rough edges. Saved workflows run by filename via run_saved_workflow (the server converts them automatically), but some node configurations still convert imperfectly.
  • Assets generated via submit_workflow may not embed workflow metadata. They might not reopen the originating workflow when opened in ComfyUI.
  • Workflow building depends on agent accuracy. Complex multi-node workflows may need a retry or refinement.
File handling
  • Outputs require a shell download step. See Outputs and downloads.
  • Upload size limits may apply depending on your MCP client. Some clients impose their own limits on file uploads.
Authentication
  • OAuth or API key. Claude Code and Claude Desktop use a one-time browser OAuth flow. Cursor requires a Comfy Cloud API key in your MCP config (no OAuth). Other headless clients can pass a Comfy Cloud API key via the X-API-Key header instead. A device-code OAuth flow for clients that cannot open a browser is planned.

FAQ

Any MCP-compatible client that supports remote HTTP transport can connect to https://cloud.comfy.org/mcp. We document first-class setup for Claude Code, Claude Desktop, Cursor, and Codex. Windsurf, Amp, OpenClaw, and other agents follow the same URL with OAuth or an API key. See Install Comfy Cloud MCP.
Not for interactive clients that support OAuth (Claude Code, Claude Desktop, Codex, and others). Cursor requires a Comfy Cloud API key in your MCP config. An API key is also needed for other headless or CI setups with no browser. See the Cursor tab or Other clients tab under Install Comfy Cloud MCP.
Paid generations are spend-gated: when a run would consume Comfy Cloud credits (a partner model, or a workflow/template with paid API nodes), the server requires your explicit agreement before executing. See Credits and spending.
No. Slash commands ship in the Claude Code plugin. Claude Desktop connects to the same MCP server (the tools work if you ask in plain language or use the prompt picker), but it does not support Claude Code plugins or slash commands.
There is no /comfy or /cloud command. Commands appear under one of two prefixes depending on how you connected:
  • Plugin (recommended): /comfy-cloud:generate-image, /comfy-cloud:generate-video, … — type /comfy-cloud: to see them all.
  • Direct connection (no plugin): /mcp__comfy-cloud__generate-image, … — type /mcp__ to see them.
Either way you can also just ask in plain language (“generate an image of …”). The MCP tools are model-invoked and do not require a slash command.
In Claude Code, run /mcp, select comfy-cloud, and choose Authenticate. In Claude Desktop, reopen the connector from Customize → Connectors and trigger sign-in.
Comfy Cloud MCP is our hosted offering, but local agent workflows have existed since ComfyUI was open-sourced. See What about local ComfyUI? on the Agent Tools overview for why Cloud shipped first, community MCP servers you can use today, and Comfy CLI as another option.