comfygenmcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| listen | No | Address this server binds to, with --transport http | 127.0.0.1:8000 |
| timeout | No | Seconds before giving up on a generation | 300 |
| comfy-url | No | Address of the ComfyUI server to generate on | http://127.0.0.1:8188 |
| transport | No | stdio, or http to listen on a port | stdio |
| no-inline-image | No | Pass --no-inline-image on the command line for a client that can't render one — it then returns only the seed and URL. | false |
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 |
|---|---|
| list_workflowsA | List the workflows saved in ComfyUI, ready ones first. Call this instead of asking the user which workflows they have -- they expect you to look. The reply separates workflows that can generate from those that cannot, because the models they reference are not installed or no prompt node was found. Only use the ready ones; naming another will fail. |
| generate_imageA | Generate an image on ComfyUI and return it inline. Returns " · seed · " plus -- unless this server was started with --no-inline-image -- the image itself. Clients usually collapse tool results, so the image is easy to miss. Pass the URL on in your reply: it survives the collapse, and is how the user sees the picture when no image is returned. Write it bare so the client turns it into a link -- code formatting or backticks make it unclickable. Use exactly the workflow name the user asked for. Similar names are different workflows -- "Krea2" and "Krea2+Upscale" are not interchangeable. Fails if the workflow needs an input image or has no prompt node to patch. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
list_workflows and generate_image are completely distinct: one discovers available workflows, the other executes generation. There is no possibility of confusing their roles.
Both tool names follow the same verb_noun pattern (list_workflows, generate_image), making the interface predictable and consistent.
At only 2 tools, the server feels thin, but the narrow scope of listing and generating ComfyUI workflows makes this minimal surface reasonable. Still, it is borderline per the calibration guideline.
The core workflow is complete: list ready workflows and generate images from them. Minor gaps exist, such as no workflow detail endpoint or explicit handling of input-image workflows, but these are edge cases rather than dead ends.