@runapi.ai/flux-2-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | Yes | Your RunAPI API key. Get one at https://runapi.ai. |
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_imageA | Create a Flux 2 task on RunAPI (remix image). Returns a task id, status, and output URLs. |
| text_to_imageB | Create a Flux 2 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-2 task. |
| check_pricingA | Look up RunAPI pricing for the flux-2 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 serves a distinct function: authentication, task status, pricing lookup, and two clearly separated image generation operations (remix vs. text-to-image). There is no overlap or ambiguity between tool purposes.
Most tool names follow a verb_noun pattern (login, get_task, check_pricing, remix_image), but text_to_image deviates by being a noun phrase rather than a verb_noun construction like create_text_to_image. The pattern is otherwise consistent and readable.
With 5 tools, the server is tightly scoped to the core workflow: authenticate, create two types of tasks, check task status, and look up pricing. This is a well-sized set with no redundant or unnecessary tools.
The tool surface covers the full lifecycle for a Flux-2 image generation service: setup (login), execution (remix_image and text_to_image), monitoring (get_task), and cost planning (check_pricing). There are no obvious gaps that would prevent an agent from completing common tasks.