comfy-image-mcp
Related Servers
Alternatives to comfy-image-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
- FlicenseAqualityDmaintenanceAn MCP server for generating images and checking generation status through ComfyUI's API. It allows interaction with local ComfyUI instances by providing workflow-based image generation and status checking tools.3-
- AlicenseAqualityBmaintenanceMCP server that connects an AI assistant to a running ComfyUI instance, allowing it to fetch saved workflows, inject a prompt and seed, run generation, and return the image inline in chat.2GPL 3.0
- FlicenseNot gradedqualityDmaintenanceMCP server that exposes ComfyUI image and 3D generation as a single tool with smart prompt classification. It enables AI assistants to generate assets directly by selecting and running the appropriate ComfyUI workflow.-
- AlicenseAqualityDmaintenanceMCP server for ComfyUI — text-to-image, variations, img2img refine, upscale, image proxy, and workflow runner.15145 npm3MIT
- FlicenseNot gradedqualityDmaintenanceMCP server exposing a local (or LAN) ComfyUI instance's HTTP API as tools, so an LLM client can queue generations, inspect the queue/history, upload reference images, browse installed models/nodes, and pull back generated images.-
TDQS
Scored across 2 tools
The two tools are clearly separated: one is a read-only diagnostic (backend/GPU/workflow status) and the other performs generation. There is no plausible way to confuse them, and image_backend_status explicitly states it does not generate anything.
Both names are snake_case and readable, but they mix a verb_noun form (generate_image) with a noun_phrase form (image_backend_status). It's a minor stylistic deviation rather than a real inconsistency.
Two tools is thin even for a narrow ComfyUI wrapper; the status tool is essentially a prerequisite check for the single real action. It's defensible for the scope but sits at the borderline of under-provisioned.
Generation plus a health check covers the core happy path, including refs for edits and cutouts, but there is no way to list previously generated images, enumerate/select configured workflows, cancel long jobs, or post-process assets. Agents will hit dead ends when they need to inspect or manage outputs.