A
licenseA
qualityC
maintenanceA 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.
23
4
Apache 2.0
comfy-draftsman
Related Servers
Alternatives to comfy-draftsman
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceAn MCP server that bridges AI agents with ComfyUI for automated workflow building, execution, monitoring, and output routing.962MIT
- 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.11 npm3Apache 2.0
- AlicenseAqualityCmaintenanceMCP server that lets AI agents drive a remote ComfyUI instance end-to-end, including queueing workflows, viewing outputs, downloading models, and authoring graphs via ComfyScript.1619,354 npm1MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that connects local ComfyUI to AI agents, enabling natural language control of ComfyUI for creating workflows, generating images, and managing the queue.-
- 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.6414GPL 3.0
TDQS
A4.1/5.0
Scored across 29 tools
Disambiguation4/5
Tools cover distinct lifecycle phases (authoring, validation, execution, delivery) and most purposes are clearly separated. Minor overlap exists among validate_workflow/lint_workflow/diagnose_workflow and get_instance_info/check_setup, but the descriptions provide enough differentiation for an agent to choose correctly.
Naming Consistency5/5
All 29 tool names follow a consistent snake_case verb_noun or action_noun pattern (e.g., get_node_info, run_workflow, save_output, search_node_packs). There is no mixing of conventions or vague naming.
Tool Count3/5
29 tools is on the heavy side for a single server, though the broad ComfyUI workflow domain (node discovery, authoring, validation, execution, model management, node-pack resolution) justifies most of them. A few closely related tools (e.g., validate/lint/diagnose, get_instance_info/check_setup) could potentially be consolidated.
Completeness5/5
The surface covers the full workflow lifecycle: node discovery and schema lookup, workflow create/import/find/list/edit/inspect/organize/lint/validate/diagnose/port, run/queue/status, output view/save, model and template listing, image upload, and persistent learning. No obvious dead ends for the stated purpose.
Maintenance
ActivityActive
ResponsivenessNo issues