@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 distinct purpose: authentication, pricing lookup, task creation, and status retrieval. There is no overlap or ambiguity between the tools, allowing an agent to select the correct one without confusion.
Tool names mostly follow a consistent snake_case verb_noun pattern (text_to_image, check_pricing, get_task). The 'login' tool is a single-word exception but is a common and recognizable auth action, so the overall consistency remains strong.
With only 4 tools, the server is well-scoped for a focused flux-kontext image generation client. Each tool serves a necessary role (auth, pricing, creation, status) with no redundancy, making the count appropriate for the domain.
The essential workflow of authentication, task creation, and status retrieval is fully covered. Missing operations like cancel or listing past tasks are minor enhancements rather than critical gaps, so the surface is reasonably complete for primary use cases.