hh-mcp-comfyui
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COMFYUI_API_BASE | No | The base URL of the local ComfyUI instance. | http://127.0.0.1:8188 |
| COMFYUI_WORKFLOWS_DIR | No | Optional path to a custom workflows directory. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_image_from_textA | |
| generate_image_from_imageA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| Generate Image with ComfyUI | Provides a starting point for generating an image using the generate_image tool. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one takes an input image for image-to-image generation, the other takes a text prompt for text-to-image generation. An agent can easily select the appropriate tool based on whether they have a reference image.
Both tool names follow a consistent 'generate_image_from_<source>' pattern (image vs text). The naming is uniform and predictable, making it easy for an agent to infer the function.
With only 2 tools, the server is very focused but slightly sparse for a general ComfyUI interface. It covers the two fundamental generation modes, which is reasonable for a minimal setup, though a few more tools (e.g., upscale or inpaint) would be expected.
The server covers the two core ComfyUI workflows (text-to-image and image-to-image), but lacks common operations like upscaling, inpainting, or workflow management. There are notable gaps that agents cannot work around.