ComfyUI MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COMFYUI_BASE_URL | Yes | The base URL of the ComfyUI server (e.g., http://127.0.0.1:8188) | |
| COMFYUI_BEARER_TOKEN | No | Optional bearer token for reverse proxies or cloud-style gateways | |
| COMFYUI_ROUTE_PREFIX | No | Optional route prefix (e.g., /api) if your endpoint is exposed under a prefix | |
| COMFYUI_TIMEOUT_SECONDS | No | Timeout in seconds for HTTP requests | 60 |
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 |
|---|---|
| comfyui_get_system_statsA | Get Python, device, and VRAM information from ComfyUI |
| comfyui_get_featuresA | Get server feature flags from ComfyUI |
| comfyui_list_modelsA | List model folders or files from |
| comfyui_get_object_infoA | Fetch node metadata from |
| comfyui_get_queueA | Get pending and running queue state from |
| comfyui_manage_queueA | Clear queue or delete pending prompt ids via POST |
| comfyui_get_historyC | Fetch history from |
| comfyui_manage_historyA | Clear history or delete prompt ids via POST |
| comfyui_submit_promptC | Submit a workflow payload to ComfyUI POST |
| comfyui_interruptB | Interrupt current execution globally or by prompt_id via POST |
| comfyui_upload_imageC | Upload an image file using POST |
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 11 tools
Each tool targets a distinct ComfyUI API endpoint or action, with clear descriptions preventing any confusion. No overlapping purposes exist.
All tools follow a consistent 'comfyui_verb_noun' pattern (e.g., comfyui_get_history, comfyui_submit_prompt), making naming predictable and easy to navigate.
With 11 tools, the set covers the essential operations for interacting with ComfyUI without being excessive or sparse. Each tool serves a clear purpose.
The tool set covers core CRUD and lifecycle operations (get, manage, submit, upload, interrupt). Minor omissions like image viewing or memory management exist, but the main workflows are complete.