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_imageC | 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_pricingA | 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: text-to-image creation, image remix, task retrieval, pricing lookup, and authentication. No overlap or ambiguity.
Most tools follow a verb_noun pattern (text_to_image, get_task, check_pricing, remix_image), with 'login' as a single-word exception. The pattern is largely consistent.
Five tools are appropriate for an image generation service, covering creation, status checking, pricing, and authentication without being excessive or insufficient.
Core operations (create, retrieve, pricing, auth) are covered. Missing potential features like task cancellation or listing are minor gaps for typical usage.