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 generation task. |
| flux_get_tasks_batchA | Query multiple Flux image generation tasks at once. |
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 6 tools
Each tool targets a distinct operation: generate vs edit, list models vs list tools, and single vs batch task queries. The cross-references in descriptions further reduce any chance of misselection.
All tools follow the consistent pattern of `flux_` prefix plus verb_noun (generate_image, list_models, get_task, etc.). The naming style is uniform and predictable across the entire set.
Six tools is well-scoped for an image generation and editing server, covering the core operations without unnecessary bloat. Each tool adds clear value to the workflow.
The core lifecycle of generating/editing images and retrieving results is well covered, along with model discovery. A minor gap is the lack of a task cancellation tool, but this is not essential for typical usage.