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 |
|---|---|
| list_workflowsB | List all ComfyUI workflow files that are available on disk. |
| read_workflowB | Read a specific workflow file by its relative path inside the configured workflow directory. |
| list_modelsB | List models exposed by the configured ComfyUI server using the object info endpoints. Specify a kind to get a flat list or use recursive mode to aggregate multiple kinds. |
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 3 tools
Each tool has a clearly distinct purpose: list_models handles model enumeration, list_workflows lists workflow files, and read_workflow reads specific workflow content. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.
All tools follow a consistent verb_noun pattern with snake_case naming: list_models, list_workflows, and read_workflow. This uniformity makes the tool set predictable and easy to understand at a glance.
With only 3 tools, the server feels thin for a ComfyUI integration, which typically involves more operations like executing workflows, managing nodes, or handling images. While the tools are well-defined, the count is borderline low for the apparent scope of interacting with a workflow automation system.
The tool set has significant gaps for a ComfyUI server, missing core operations such as executing workflows, uploading or managing models, and handling generated outputs. This incomplete surface will likely cause agent failures when trying to perform typical ComfyUI tasks beyond basic listing and reading.