Comfy MCP is an officially maintained, local-first MCP server from Comfy-Org built on comfy-cli. It runs as a stdio subprocess of your client and drives the ComfyUI on your own machine, covering generation, job monitoring, output collection, live introspection of your installed nodes/models/templates, and workflow validation and management. It is local-first but not local-only: partner models run on partner infrastructure, and COMFYUI_URL can target a machine you control. It has no path to Comfy Cloud, so tie into the separate remote HTTP server for cloud GPU execution. It needs Python >= 3.10 and comfy-cli >= 1.14.0, is beta, and exposes around 40 tools. It suits users with local inference hardware who want to automate a local ComfyUI from an AI client; credit spend, network exposure and local environment changes are the main risks, each behind a confirmation gate that still deserves careful authorization.
Comfy MCP is a local MCP server maintained by Comfy-Org and built on comfy-cli. It is launched as a stdio subprocess by your AI client and drives the ComfyUI installed on your own machine (default 127.0.0.1:8188, or one on another machine you control via COMFYUI_URL / COMFYUI_HOST). It can generate images, submit and monitor jobs asynchronously, surface failure verdicts, collect output PNGs, introspect the nodes/models/templates your live install actually has, validate and edit workflows, and launch/stop/restart ComfyUI and tail its logs. Every tool shells out to the comfy command with --where local --json and parses comfy-cli's envelope/1 output. It requires Python >= 3.10, comfy-cli >= 1.14.0, a ComfyUI workspace and a running ComfyUI. It is currently beta, with 40 tools. Note it has no path to Comfy Cloud; for cloud-hosted execution use the separate remote HTTP server at https://cloud.comfy.org/mcp.
{
"mcpServers": {
"comfy-mcp": {
"command": "comfy-mcp",
"env": {
"COMFY_BIN": "/path/to/venv/bin/comfy",
"COMFY_API_KEY": "<your-comfy-api-key>"
}
}
}
}