@runapi.ai/flux-kontext-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | Yes | Your RunAPI API key. Can also be stored in ~/.config/runapi/config.json. |
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. |
| text_to_imageB | Create a Flux Kontext 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-kontext task. |
| check_pricingB | Look up RunAPI pricing for the flux-kontext 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 4 tools
Each tool has a clear, unique purpose: login handles authentication, text_to_image creates tasks, get_task retrieves task status, and check_pricing provides pricing info. There is no overlap or ambiguity between them.
All tool names use consistent snake_case and follow clear verb-based patterns (e.g., text_to_image, get_task, check_pricing). The naming is predictable and easy to understand.
With 4 tools, the server is well-scoped for its purpose: authentication, image generation, task polling, and pricing lookup. This is a focused and efficient set without unnecessary extras.
The tools cover the essential lifecycle: authenticate, create a task, check status, and get pricing. A minor gap is the lack of a list all tasks tool, which may require users to remember task IDs, but core workflows are supported.