comfy-mcp-local
Related Servers
Alternatives to comfy-mcp-local
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to plan and apply ComfyUI canvas changes node by node, with human approval in manual mode, live execution progress, logs, file monitoring, and node-knowledge validation.16MIT
- AlicenseAqualityCmaintenanceA local Model Context Protocol server that lets MCP hosts inspect and edit the workflow currently open on a live ComfyUI canvas, including node and group operations applied as atomic undoable transactions.536 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to control ComfyUI workflows through isolated local reverse proxies and a browser workflow bridge, including connecting to backends, editing and saving workflow graphs, transferring files, and submitting runs.1MIT
- 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 gradedqualityBmaintenanceEnables remote AI agents to control a local, authenticated desktop browser over MCP through an outbound WebSocket bridge and Chrome extension, supporting tab management, navigation, page reading, clicking, typing, scrolling, screenshots, and JavaScript evaluation.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables local opencode agents to control a live Chrome browser via MCP tools, including tab management, JavaScript execution, clicking, form filling, page reading, screenshots, and console log retrieval.3MIT
TDQS
Scored across 39 tools
Most tools are distinct, but several pairs overlap: `run_workflow` vs `run_template` vs `generate_image` all execute generation; `download_model` vs `download` (tracker) vs `fetch_outputs` (downloads outputs) could confuse; `nodes` vs `node_dependencies` vs `workflow_deps` are related but distinct. Descriptions are detailed enough to disambiguate with careful reading, but the boundaries between run/execute tools and download-related tools require effort.
Most tools follow a clear verb_noun pattern: `search_templates`, `get_template`, `fetch_template`, `run_workflow`, `validate_workflow`, `list_workflow_slots`, `set_workflow_slot`, `vary_workflow`, `list_partner_models`, `partner_model_schema`, `partner_generate`, `emit_partner_workflow`, `download_model`, `upload_file`, `install_node`, `update_comfyui`, `restart_comfyui`, `stop_comfyui`, `launch_comfyui`. Minor deviations: `job` and `download` are bare nouns with action parameters rather than verb_noun; `which` is a bare verb; `nodes` is a bare noun. The pattern is strong but not universal.
39 tools is a very large surface for an MCP server. While the domain (ComfyUI/comfy-cli management) is broad, many tools wrap subcommands of a single CLI and could be consolidated (e.g., `job` already multiplexes five actions; `download` multiplexes three; `nodes` multiplexes seven). The count exceeds the 25+ threshold for 'too many' and will burden an agent's context window and tool-selection accuracy.
The tool surface covers the core lifecycle well: server management (launch/stop/restart/update/switch), workflow execution (run/validate/slots/vary), template on-ramp (search/get/fetch/run), model management (search/download/upload), job tracking (status/wait/watch/cancel), and diagnostics (server_info/system_stats/get_logs/free_memory). Minor gaps: no direct tool for listing uploaded files in the input directory, no tool for deleting/removing models, and no explicit tool for viewing workflow history beyond `job(action="queue")`. These are workable gaps, not dead ends.