MCP ComfyUI Flux
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_imageC | Generate an image using Flux dev model in ComfyUI |
| connect_comfyuiC | Connect to ComfyUI server |
| disconnect_comfyuiB | Disconnect from ComfyUI server |
| check_modelsC | Check if Flux dev model is available in ComfyUI |
| remove_backgroundC | Remove background from an image using AI-powered segmentation |
| upscale_imageC | Upscale an image using AI models |
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 6 tools
Each tool has a clearly distinct purpose: model checking, connection management, image generation, and two distinct post-processing operations. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case, making them predictable and easy to understand.
With 6 tools covering connection, model check, generation, and post-processing, the number is well-scoped for the server's purpose.
The tool set covers core workflows (connect, check, generate) and adds useful post-processing. Minor gap: only checks for one specific model; a general model listing could be useful.