Local vs. Comfy Cloud agent

If you’re deciding between Comfy-Org’s official agent tooling and this project, the short version is that they solve different problems — and for a decent number of people the official option is the right call. This page lays out both honestly so you can pick once and move on.

​

The one-line answer

No local GPU, or you want zero setup? Use Comfy Cloud. It’s first-party, it’s maintained by the team that builds ComfyUI, and you don’t have to think about drivers, VRAM, or model downloads. Already running ComfyUI on your own machine? That’s what this project is for. Your GPU is already paid for, your models are already on disk, and your Claude or ChatGPT subscription already covers the reasoning.

​

What Comfy-Org offers

Comfy-Org’s Agent Tools page lists three relevant products: Comfy Cloud MCP is genuinely good at what it does: it exposes the ComfyUI engine over MCP, signs in with OAuth from Claude Code, Claude Desktop, and Codex, and gives you managed access to models like Kling, Veo, Seedance, Flux, and ElevenLabs without owning a GPU.

​

What this project offers

comfyui-mcp is an MCP server plus a sidebar agent that drives your ComfyUI install — local, LAN, VPS, or RunPod. 38 MCP tools, 42 model-specific skills, and a panel agent that edits your live graph in natural language. The structural difference is where the reasoning comes from. This project is provider-agnostic: the same tools and the same panel run on Claude, ChatGPT, Gemini, Grok, or Kimi using a subscription you already pay for, on any OpenAI-compatible endpoint, or on a free local model through Ollama, LM Studio, or llama.cpp — with no account and no outbound network at all.

​

Side by side

​

Choose Comfy Cloud if…

• You don’t have a GPU, or yours is too small for the models you want
• You want it to work with no setup and no maintenance
• You’d rather buy credits than manage CUDA, VRAM, and checkpoint downloads
• Your team is already on Comfy Cloud and you want one vendor and one invoice
• You want first-party support from the people who build ComfyUI

These are good reasons. If several apply to you, stop reading and go use Comfy Cloud — you’ll have a better time.

​

Choose comfyui-mcp if…

• You already have a GPU. You’ve paid for it; cloud credits are a second bill for compute you already own.
• Your work can’t leave the machine. Client material under NDA, licensed training data, anything you can’t upload. With a local model, nothing does.
• You want to use the LLM subscription you already have. Your Claude or ChatGPT plan already covers the reasoning — no second meter for the agent.
• You want it free, or you want it offline. Ollama, LM Studio, and llama.cpp run with no account and no network. See Local LLMs.
• Your install is the point. Your custom nodes, your LoRAs, your checkpoint collection. The agent installs nodes and downloads models into the install you actually use.
• You want to choose the model. Different LLMs are better at different things; the LLM Arena scores them on real ComfyUI tasks so you can pick on evidence. See Backends.

​

”Won’t the official local MCP make this redundant?”

Fair question, and worth answering directly rather than pretending otherwise. Comfy Local MCP is a first-party driver for a local install, and when it ships it will be a good one. But it is a different layer than this project: it connects an agent to ComfyUI, where comfyui-mcp also brings the agent, the provider-neutral backend that runs it across eleven providers and local runtimes, the sidebar UI, the model-specific skills, and the node/model management. The honest read: if all you want is “let Claude Code talk to my local ComfyUI,” first-party tooling will eventually cover that, and you should probably use it. If you want to bring your own model — including a free local one — and have the agent live inside ComfyUI and manage the install itself, that’s the gap this project exists to fill. They also compose. This project can target Comfy Cloud too (set COMFYUI_API_KEY — see Cloud deployment), so one config covers a local install, a LAN box, a VPS, and Comfy Cloud.

​

Getting started