comfyui-mcp-server
Related Servers
Alternatives to comfyui-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceExposes the workflows saved in a ComfyUI server (local, remote, or vast.ai) as MCP tools, letting agents list them, inspect their inputs, and run them with their own prompts, images, seeds, and per-run node toggles. It also reports server/GPU status, tracks and downloads job outputs, and uploads images or browses model folders.10-
- AlicenseNot gradedqualityDmaintenanceGive AI agents full control over your local ComfyUI by exposing 77 tools for workflow management, image generation, model handling, and real-time canvas control.4AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables an AI agent to generate images on a remote ComfyUI machine by invoking named, swappable exported ComfyUI API workflows and save the results into a local workspace directory.MIT
- AlicenseAqualityDmaintenanceEnables comprehensive ComfyUI workflow automation including image generation, workflow management, node discovery, and system monitoring through natural language interactions with local or remote ComfyUI servers.3163 PyPI14MIT
- AlicenseNot gradedqualityBmaintenanceEnables an AI client to run pre-reviewed local ComfyUI workflows using only whitelisted parameters, submit labeled batch runs, track persisted status, and fetch paginated results without sending full graphs or image data into the conversation.MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to remotely control a ComfyUI installation via its HTTP API, including generating and editing images, creating transparent assets, generating video and audio, tracking the queue, and downloading results.20MIT
TDQS
Scored across 13 tools
The core generation matrix is reasonably separable (generate_image vs generate_ipadapter vs batch_generate vs batch_generate_ipadapter), but system_check and get_vram_usage both read driver-level GPU/VRAM data and are easy to swap, and get_comfyui_status vs get_job_status are only distinguished by careful reading. Four near-parallel generation tools plus two overlapping health tools make misselection plausible without studying descriptions.
All names are snake_case and mostly verb-first (get_vram_usage, get_job_status, start_comfyui, list_models). Minor deviations: system_check is noun-first, the comfyui_ prefix is applied inconsistently (start_comfyui/stop_comfyui but not generate_image), and batch variants use a prefix while single variants use a suffix.
Thirteen tools is well within a healthy range and each maps to a distinct operational need: lifecycle control, monitoring, model management, and four generation paths. Nothing feels padded or missing at the count level.
Lifecycle (start/stop/status), GPU monitoring/cleanup, model discovery and download, async generation with polling, plus batch and IP-Adapter variants give broad coverage. Gaps remain: no cancel/abort job, no queue management or job listing, and no way to run custom or list stored workflows.