ComfyUI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_imageC | Generate an image using ComfyUI |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The tool's purpose is clearly defined and distinct by default.
Since there is only one tool, naming consistency is inherently perfect with no deviations or mixed conventions to evaluate. The tool name 'generate_image' follows a clear verb_noun pattern.
A single tool is too few for a server named 'ComfyUI MCP Server', which suggests a broader scope related to image generation workflows. This minimal set likely leaves significant functionality uncovered, making it feel thin and incomplete.
The server is severely incomplete for its apparent domain of ComfyUI image generation, as it only offers image generation without any supporting operations like listing workflows, managing nodes, or handling outputs. This single tool creates dead ends and will cause agent failures in complex tasks.