mcp-comfy-ui-builder
Related Servers
Alternatives to mcp-comfy-ui-builder
No user-submitted related servers found.
Related Servers
- 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.3138 PyPI14MIT
- FlicenseBqualityDmaintenanceConnects AI assistants to ComfyUI for image, video, and audio generation, providing full control over ComfyUI through 40+ tools including quick generation, cloud API nodes, and custom workflow building.46-
- FlicenseBqualityDmaintenanceEnables orchestration of ComfyUI workflows through natural language by discovering workflow templates, applying mutations, and submitting prompts to running ComfyUI instances. Provides asset validation and lightweight tooling for AI image generation experimentation.3-
- AlicenseNot gradedqualityCmaintenanceGive AI agents full control over your local ComfyUI by exposing 77 tools for workflow management, image generation, model handling, and real-time canvas control.3AGPL 3.0
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to generate and iteratively refine images, audio, and video by interacting with a local ComfyUI instance through natural conversation. It provides comprehensive tools for workflow management, node introspection, and publishing generated assets.Apache 2.0
- 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 61 tools
Several tools have heavily overlapping boundaries: finalize_workflow is explicitly identical to get_workflow_json; execute_workflow_sync vs execute_workflow_stream vs get_execution_status/progress/history/last_output are multiple paths to similar monitoring; download_output/download_by_filename/download_all_outputs overlap; and node discovery is spread across list_node_types, search_nodes, discover_nodes_live, suggest_nodes, and get_node_info. Descriptions help, but an agent must still reason carefully to pick the right tool for many common tasks.
Names are consistently snake_case and mostly follow verb_noun patterns such as list_models, get_model_info, execute_workflow, and download_output. Minor deviations exist (interrupt_execution, clear_queue, apply_template) and a few near-duplicate names like finalize_workflow vs get_workflow_json weaken predictability, but overall the convention is readable.
With 61 tools, the surface is far too large for a coherent single server. Many capabilities are split into multiple similar tools rather than consolidated, making the set difficult to navigate and increasing selection errors.
Coverage is broad: node discovery, workflow construction, templates, macros, execution, queue control, output download, model management, plugin reloading, and saved-workflow persistence are all represented. Minor gaps remain, such as deleting saved workflows, but core ComfyUI lifecycle workflows are well covered.