FluxMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level | INFO |
| MCP_SERVER_NAME | No | MCP server name | flux |
| FLUX_REQUEST_TIMEOUT | No | Request timeout in seconds | 1800 |
| ACEDATACLOUD_API_TOKEN | Yes | API token from AceDataCloud | |
| ACEDATACLOUD_API_BASE_URL | No | API base URL | https://api.acedata.cloud |
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 |
|---|---|
| flux_generate_imageA | Generate AI images from a text prompt using Flux. |
| flux_edit_imageA | Edit an existing image using Flux with a text prompt. |
| flux_list_modelsA | List all available Flux models and their capabilities. |
| flux_list_actionsA | List all available Flux tools and their use cases. |
| flux_get_taskA | Query the status and result of a Flux image or video generation task. |
| flux_get_tasks_batchA | Query multiple Flux image or video generation tasks at once. |
| flux_generate_videoB | Generate text/image/video-to-video or enhance an owned temporary draft. Poll flux_get_task. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| flux_image_generation_guide | Guide for choosing the right Flux tool and model for image tasks. |
| flux_prompt_writing_guide | Best practices for writing effective Flux image generation prompts. |
| flux_workflow_examples | Common workflow examples for Flux image generation. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
flux_generate_image and flux_edit_image are clearly distinguished by their generation vs. editing semantics, and flux_get_task vs. flux_get_tasks_batch differ by singular/plural. However, the action of checking generation status is split across three tools (get_task, get_tasks_batch, and the generate_* tools that return task IDs), which could create minor confusion about when to poll.
All tools follow a consistent flux_verb_noun pattern: get_task, edit_image, get_tasks_batch, generate_video, generate_image, list_actions, list_models. The only variation is the plural 'tasks' in get_tasks_batch, which is a natural and readable exception.
Seven tools is well-scoped for an image/video generation service. It covers generation, editing, status checking, batch status, and two reference lists without redundancy.
Core workflows are covered: generate image/video, edit image, poll status (single and batch), and list models/actions. Minor gaps include no explicit cancellation or deletion of tasks, and no way to list past tasks, but agents can work around these.