comfyui-mcp-secure
Related Servers
Alternatives to comfyui-mcp-secure
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server that exposes ComfyUI image and 3D generation as a single tool with smart prompt classification. It enables AI assistants to generate assets directly by selecting and running the appropriate ComfyUI workflow.-
- 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.-
- AlicenseAqualityDmaintenanceMCP server for ComfyUI — text-to-image, variations, img2img refine, upscale, image proxy, and workflow runner.1584 npm1MIT
- AlicenseAqualityAmaintenanceMCP server that connects an AI assistant to a running ComfyUI instance, allowing it to fetch saved workflows, inject a prompt and seed, run generation, and return the image inline in chat.2GPL 3.0
- AlicenseBqualityBmaintenanceAn MCP server that bridges AI agents with ComfyUI for automated workflow building, execution, monitoring, and output routing.961MIT
- 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
TDQS
Scored across 46 tools
There are several overlapping tool pairs, notably comfyui_get_queue vs comfyui_get_queue_status, and comfyui_get_history vs comfyui_list_jobs vs comfyui_get_job. The descriptions are detailed and cross-referenced, so the boundaries are clear on close reading, but an agent could easily misselect between these similar-purpose tools.
Every tool uses the consistent comfyui_ prefix followed by a snake_case verb_noun pattern (list_models, create_workflow, cancel_job). No mixed camelCase or irregular verb usage; parallel operations share the same verb (get_, list_, run_, upload_), making the naming predictable and easy to navigate.
At 46 tools, the set is well above the 25+ threshold where it becomes hard to discover and choose among options. While each tool is individually purposeful, the surface could be consolidated—for example, merging queue-status variants and unifying history/job listing—to make the server more manageable.
The tool set provides broad coverage of the ComfyUI domain: workflow creation/validation/modification/execution, image manipulation (transform, inpaint, upscale), model and custom-node management, and queue/job lifecycle control. Minor gaps like deleting models/images or retrying failed jobs exist but are easily worked around.