ComfyUI MCP Server
Related Servers
Alternatives to ComfyUI MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables Claude to generate images via ComfyUI from natural language requests, automating workflow construction and execution.1MIT
- FlicenseNot gradedqualityDmaintenanceBridges Claude Desktop to local and remote ComfyUI instances, enabling health checks, model listing, workflow queuing, status polling, and output retrieval.-
- AlicenseNot gradedqualityDmaintenanceEnables Claude to generate images through a local ComfyUI instance using Stable Diffusion and SDXL models via natural language. Users can trigger image generation, list available checkpoint models, and monitor the ComfyUI queue status directly from their MCP client.MIT
- 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.3114MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to interact with local ComfyUI installations to list nodes, validate workflows, and execute image generation workflows directly without requiring an HTTP server.1MIT
- AlicenseAqualityBmaintenanceMCP server + Claude Code plugin for ComfyUI — execute workflows, generate images, visualize pipelines, manage models, control VRAM, and explore custom nodes, all from your AI coding assistant.4835,030 npm1MIT
TDQS
Scored across 14 tools
Each tool has a clearly distinct purpose with no ambiguity. For example, comfy_generate_simple is for quick image generation, comfy_submit_workflow handles complete workflow execution, and comfy_get_status monitors progress, all targeting different aspects of the ComfyUI workflow lifecycle. The descriptions clearly differentiate between queue management, workflow management, generation, and output handling.
All tools follow a consistent comfy_verb_noun pattern with snake_case throughout. The naming convention is predictable and readable, such as comfy_list_workflows, comfy_save_workflow, and comfy_cancel_generation. This uniformity helps agents easily identify and select the appropriate tools.
With 14 tools, the count is well-scoped for managing ComfyUI workflows, covering generation, queue management, workflow storage, and output retrieval. Each tool earns its place by addressing specific needs in the image generation pipeline, from submission to completion, without being excessive or insufficient.
The tool surface provides complete coverage for the ComfyUI domain, including CRUD operations for workflows (list, load, save, delete), generation lifecycle (submit, cancel, wait, status), queue management (get, clear), and output handling (get images, upload image). There are no obvious gaps, enabling agents to handle end-to-end workflows seamlessly.