comfy-mcp
Related Servers
Alternatives to comfy-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to generate and edit images using local Stable Diffusion models in ComfyUI, with tools for text-to-image, img2img, ControlNet, UI frames, upscaling, and background removal—no cloud API or API key required.MIT
- 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 gradedqualityBmaintenanceTurns curated ComfyUI workflows into typed MCP tools and REST endpoints, enabling image generation and job management through natural language or HTTP calls.MIT
- AlicenseNot gradedqualityBmaintenanceExposes ComfyUI workflows as 12 MCP tools on ComfyUI's own port, letting AI agents generate, edit, and remove backgrounds from images plus create videos by passing semantic parameters instead of whole workflow graphs. Agents can list models, submit and track async tasks, fetch artifact URLs, and jump to a visual asset/task page.2MIT
- 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
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to generate and iteratively refine images, audio, and video through natural conversation using a local ComfyUI instance.AGPL 3.0
TDQS
Scored across 8 tools
Each tool targets a distinct concern: generation, editing, server/model inspection, and job lifecycle management. The job-related tools (status, wait, fetch, cancel) are clearly differentiated by their blocking behavior and return payload.
Most tools follow a clear verb_noun pattern: generate_image, edit_image, list_models, fetch_result, cancel_job. The two status tools (server_status, job_status) are noun-first, which is a minor deviation but still readable and internally consistent.
Eight tools is well-scoped for an image generation/editing server with asynchronous job support. Each tool serves a clear purpose without redundancy or bloat.
The surface covers the full generation/edit workflow plus model discovery, server health, and complete job lifecycle management (status, wait, fetch, cancel). No critical operations are missing for the stated domain.