iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To control a local ComfyUI installation from Claude Code or Cursor, install both comfy-mcp and comfy-cli (version 1.14.0 or newer), start ComfyUI, and register the local MCP server in your client. Installing comfy-mcp alone does not install the CLI or ComfyUI. The steps below cover the prerequisites, configuration for each client, and common connection problems.
What you need before connecting
- Python 3.10 or newer.
comfy-cli1.14.0 or newer. The MCP server calls thecomfyexecutable available on its process’sPATH, or the executable specified withCOMFY_BIN. It does not bundle or install comfy-cli.- A ComfyUI installation or workspace. If you do not already have one,
comfy installcreates a workspace. - A running ComfyUI service. Start it with
comfy launchand leave it running before asking the agent to run workflows.
The project’s documented minimum CLI version can change. Its version check exists because older comfy-cli releases do not support enough of the MCP server’s tools. See the comfy-mcp repository for the current requirement.
Install and start ComfyUI
Run these commands in a terminal where Python and comfy-cli are available. If you already have a ComfyUI workspace, you can skip the installation command.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →- Install the MCP server and CLI:
pip install comfy-mcp "comfy-cli>=1.14.0" - Create a ComfyUI workspace if needed:
comfy install - Start ComfyUI and keep it running:
comfy launch
The agent’s MCP server process must be able to find the same comfy executable. If the terminal can run comfy but the client later reports that it is missing, set COMFY_BIN to the executable’s absolute path in the client configuration.
#1 Best Overall
Connect Claude Code
Register the local stdio server from a terminal with Claude Code installed:
claude mcp add comfy-mcp -- comfy-mcpThis launches comfy-mcp as a local subprocess. If Claude Code needs an explicit path to comfy-cli, pass COMFY_BIN as an environment variable when registering the server:
claude mcp add comfy-mcp -e COMFY_BIN=/absolute/path/to/comfy -- comfy-mcpThe repository also documents using a project-level .mcp.json entry with comfy-mcp as the server command. For nodes that use partner APIs, COMFY_API_KEY is optional; it is not required merely to connect to local ComfyUI.
Rank #2
After registration, restart or reload Claude Code so it discovers the server and its tools.
Connect Cursor
In Cursor, add a local server entry to either the user-wide ~/.cursor/mcp.json file or the project’s .cursor/mcp.json. A basic configuration is:
{
"mcpServers": {
"comfy-mcp": {
"command": "comfy-mcp"
}
}
}If Cursor cannot locate the intended comfy-cli executable, set COMFY_BIN in the server entry’s environment:
{
"mcpServers": {
"comfy-mcp": {
"command": "comfy-mcp",
"env": {
"COMFY_BIN": "/absolute/path/to/comfy"
}
}
}
}Save the file, then restart or reload Cursor to make the new MCP tools available.
Verify the connection and run a workflow
Once the client has reloaded, ask the agent to check that local ComfyUI is running and execute a workflow, for example:
Confirm my local ComfyUI is running, then run the workflow at
~/workflows/txt2img.jsonand show me the image.
The server offers tools for workflow execution, asynchronous job monitoring and cancellation, output retrieval, workflow validation and template editing, and inspection of available nodes, models, and templates. It can also manage the ComfyUI process and access logs. The repository describes the project as beta and lists a 40-tool surface at the time documented; the available tools and successful results depend on the installed versions and local environment.
Connection does not guarantee that a workflow will run. Its required custom nodes, models, and other dependencies must be present in the ComfyUI environment. The server’s inspection and validation tools can help identify missing requirements. Comfy’s announcement also describes checking available hardware when considering whether a model is suitable, but it does not set a universal GPU minimum or recommend a particular card.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesLocal ComfyUI or Comfy Cloud?
Local Comfy MCP and the Cloud connection are separate options: the local server is a subprocess that controls ComfyUI on your machine, while the Cloud connection is a remote HTTP service that runs workflows on Comfy Cloud GPUs.
| Consideration | Local ComfyUI | Comfy Cloud |
|---|---|---|
| Where workflows run | Your machine’s ComfyUI installation | Comfy Cloud GPUs |
| Local installation | Requires a ComfyUI installation and running service | A local ComfyUI installation is not required |
| Local models and custom nodes | Can use those available in the local ComfyUI environment | Uses the Cloud execution environment rather than local files and nodes |
| Cost terms | The Comfy support article says local generation runs on your hardware without Cloud-generation charges; partner models may use credits. | The Comfy support article says Cloud generation requires an active subscription. |
These cost terms are described in Comfy’s MCP setup guide and may change. That guide identifies Cloud as an option for people who want to avoid local installation or hardware, including users of browser-based assistants. It also says the local and Cloud connections can both be used, but are distinct and authenticate separately.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot common setup problems
The client connects, but tool calls say comfy is missing
Install comfy-cli 1.14.0 or newer and check that the client-launched server process can see it. If the executable is outside that process’s PATH, configure COMFY_BIN with the absolute path to the intended comfy executable.
The MCP server is configured, but its tools do not appear
Restart or reload Claude Code or Cursor after changing the MCP configuration. Confirm the server command is comfy-mcp and that the JSON is valid in Cursor’s configuration file.
Free tools Windows power users keep installed
One-click scans. No signup required.
macOS blocks access to the installation
Comfy’s repository notes that macOS privacy protections may block an installation located in Documents, Desktop, or Downloads. Move it to an unprotected directory, or grant Full Disk Access to the relevant client or terminal, then restart that app.
The connection works, but a workflow fails
Check that ComfyUI is still running, then confirm the workflow’s required nodes, models, and dependencies are installed in that ComfyUI environment. A connected MCP server cannot supply missing local workflow components automatically.
