Flux MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | No | Useful for headless and CI hosts. The server resolves auth in this order: 1. RUNAPI_API_KEY environment variable; 2. ~/.config/runapi/config.json, created by the MCP login tool or runapi login; 3. No key, which still allows check_pricing. A pre-provisioned headless config can use {"apiKey": "your_runapi_key"}. |
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": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loginA | Authenticate RunAPI by opening a browser PKCE login flow and saving the API key to ~/.config/runapi/config.json. |
| remix_imageB | Create a Flux task on RunAPI (remix image). Returns a task id, status, and output URLs. |
| text_to_imageB | Create a Flux task on RunAPI (text to image). Returns a task id, status, and output URLs. |
| get_taskA | Fetch the current status and latest result payload for a flux task. |
| check_pricingB | Look up RunAPI pricing for the flux model line. |
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 5 tools
Each tool targets a distinct action: authenticate (login), create a task (remix_image, text_to_image), poll a task (get_task), and look up cost (check_pricing). The two creation tools overlap in returning a task id but are clearly separated by input modality, so misselection is unlikely.
All names use snake_case, and most follow a verb_noun pattern (get_task, remix_image, check_pricing). The lone bare verb (login) and the noun-style text_to_image are minor deviations that don't hurt readability.
Five tools is a lean but reasonable surface for a single-purpose image-generation API: auth, two generation modes, task polling, and pricing. It is slightly thin, with no list or cancel operations, but nothing feels redundant.
The core workflow is covered end-to-end: authenticate, submit a task, poll its status/result, and check pricing. Minor gaps exist (no task listing, cancellation, or delete), but agents can work around these by tracking task ids themselves.