comfy-mcp-local
Related Servers
Alternatives to comfy-mcp-local
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceA 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.5442 npmMIT
- 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 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 gradedqualityAmaintenanceEnables 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.MIT
- AlicenseAqualityAmaintenanceEnables AI agents to inspect and edit the live browser-resident canvas of the Boarderless app via a structured spatial ledger.98 npm1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to collaboratively draw and annotate Excalidraw diagrams in real-time via MCP tools, synced to a browser canvas.8Apache 2.0
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.