ComfyUI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FAL_KEY | No | Your fal.ai API key for cloud GPU inference | |
| COMFY_URL | No | ComfyUI server URL | http://localhost:8188 |
| OUTPUT_MODE | No | Output mode: file (Image) or url (string URL) | file |
| POLL_TIMEOUT | No | Max seconds to wait for workflow (1-300) | 60 |
| POLL_INTERVAL | No | Seconds between status polls (0.1-10.0) | 1.0 |
| OUTPUT_NODE_ID | No | Default output node ID | |
| PROMPT_NODE_ID | No | Default prompt node ID for generate_image | |
| COMFY_URL_EXTERNAL | No | External URL for image retrieval (defaults to same as COMFY_URL) | |
| COMFY_WORKFLOWS_DIR | No | Directory for API format workflows (execution) | |
| COMFY_WORKFLOWS_UI_DIR | No | Directory for UI format workflows (editor) | |
| COMFY_WORKFLOW_JSON_FILE | No | Default workflow file for generate_image |
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 |
|---|---|
| get_system_statsA | Get ComfyUI server health: version, memory, device info. |
| get_queue_statusA | Get current queue: running and pending jobs. |
| get_historyB | Get recent generation history. |
| cancel_currentB | Interrupt current generation. |
| clear_queueB | Clear the queue or delete specific items. |
| list_nodesA | List available ComfyUI nodes. |
| get_node_infoA | Get detailed info about a node. |
| list_modelsA | List available models in a folder. |
| list_model_foldersA | List available model folder types. |
| list_embeddingsB | List available text embeddings. Returns list of embedding names that can be used in prompts. |
| list_extensionsA | List loaded ComfyUI extensions. Returns list of installed extension names (custom node packs). Use this to verify which custom nodes are available (e.g., fal.ai connector). |
| refresh_nodesA | Refresh the node cache. |
| search_nodesC | Search for nodes by name, category, or description. |
| list_workflowsA | List available workflow files. |
| load_workflowC | Load a workflow file for inspection or modification. |
| save_workflowA | Save a workflow to the workflows directory. |
| create_workflowA | Create an empty workflow structure. |
| generate_workflow_nameA | Generate a random funny workflow name. |
| add_nodeA | Add a node to a workflow. |
| remove_nodeA | Remove a node from a workflow. |
| update_node_inputC | Update a specific input on a node. |
| get_workflow_templateB | Get a pre-built workflow template. |
| list_templatesB | List available workflow templates. |
| validate_workflowC | Validate a workflow structure. |
| convert_workflow_to_uiA | Convert an API format workflow to UI/Litegraph format. |
| run_workflowC | Execute a saved workflow file. |
| execute_workflowB | Execute an arbitrary workflow dict. |
| generate_imageA | Generate an image using the default workflow. |
| submit_workflowA | Submit a workflow without waiting for completion. |
| get_prompt_statusB | Get the status of a submitted prompt. |
| get_result_imageA | Get the result image from a completed prompt. |
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 31 tools
Most tools have distinct purposes, but there is some overlap between execute_workflow, run_workflow, and generate_image that could cause confusion. For example, generate_image is described as a simplified interface, but its relationship to the other execution tools isn't entirely clear from the descriptions alone. However, the majority of tools target specific operations like workflow management, node handling, and system monitoring.
Tool names follow a consistent verb_noun pattern throughout, such as add_node, cancel_current, clear_queue, and get_history. There are no deviations in naming conventions, making it easy to predict what each tool does based on its name. This consistency enhances usability for agents.
With 31 tools, the count is borderline high for a single server, potentially overwhelming for agents. While ComfyUI is a complex system with many operations, some tools like generate_workflow_name and get_system_stats might be considered non-essential, contributing to a slightly bloated interface. A more focused set could improve coherence.
The tool surface comprehensively covers the ComfyUI domain, including workflow creation, modification, execution, monitoring, and system management. It supports full CRUD-like operations for workflows and nodes, provides templates and history, and handles edge cases like validation and conversion. No obvious gaps are present for the stated purpose.