F
licenseNot graded
qualityB
maintenanceMCP server that connects local ComfyUI to AI agents, enabling natural language control of ComfyUI for creating workflows, generating images, and managing the queue.
-
ComfyPilot
by dreamrec
Related Servers
Alternatives to ComfyPilot
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that enables AI agents to control a local ComfyUI instance for image generation, allowing workflow understanding, parameter modification, execution, and model discovery.23 npm3Apache 2.0
- AlicenseAqualityAmaintenanceAn MCP server that integrates with a local ComfyUI, allowing assistants to list and run workflows, monitor progress, and view results, as well as read and edit the live workflow canvas via an optional bridge node.6411GPL 3.0
- AlicenseAqualityCmaintenanceA universal MCP server that lets agents discover ComfyUI nodes, build/edit/run API workflows, manage queues, retrieve outputs, and optionally render graphs on a ComfyUI canvas.232Apache 2.0
- AlicenseAqualityAmaintenanceThe MCP server that drafts ComfyUI workflows a human can actually read. It lets coding agents build, repair, port, validate, and run ComfyUI workflows against your own ComfyUI instance, delivering clean, organized, fully-labeled workflows.292MIT
- AlicenseNot gradedqualityCmaintenanceA lightweight MCP server that bridges AI agents with a local ComfyUI instance to generate and iteratively refine images, audio, and video through conversational tool calls.18 npmMIT
TDQS
B3.3/5.0
Scored across 96 tools
Disambiguation2/5
The tool set has several near-overlapping clusters: comfy_get_status and comfy_describe_dynamics both return queue/event/execution snapshots; list_output_images, list_artifacts, and download_batch all cover output metadata listing; list_extensions and list_installed_nodes are redundant. With 96 tools, an agent will frequently struggle to pick the precise tool for a task despite good individual descriptions.
Naming Consistency4/5
Almost all tools share the comfy_ prefix and snake_case convention, and the majority follow a clear verb_noun pattern such as list_models, get_queue, and upload_image. However, there are notable deviations like comfy_instance_doctor, comfy_interrupt, comfy_sweep, and get_model_info, whose name misleadingly suggests model file metadata rather than node schema.
Tool Count1/5
96 tools is far beyond a manageable MCP surface and reflects extreme scope creep rather than disciplined coverage. Many tools handle narrow sub-tasks that could be merged or moved into separate focused servers, and the count alone will overwhelm an agent's tool-selection process.
Completeness4/5
The server covers nearly every major ComfyUI lifecycle area: instance discovery, queue/job management, workflow build/validate/queue, model and node inspection, image and artifact handling, snapshots, techniques, blueprints, and safety controls. Minor gaps remain, such as no delete/update operations for techniques or blueprints and some redundant history/job APIs, but no critical dead-end prevents the core workflow.
Maintenance
ActivityMaintained
ResponsivenessNo issues