RunAPI Qwen Image MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | No | API key for RunAPI, used for headless and CI hosts. Resolves auth before the config file. |
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. |
| edit_imageB | Create a Qwen Image task on RunAPI (edit image). Returns a task id, status, and output URLs. |
| remix_imageB | Create a Qwen Image task on RunAPI (remix image). Returns a task id, status, and output URLs. |
| text_to_imageB | Create a Qwen Image 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 qwen-image task. |
| check_pricingB | Look up RunAPI pricing for the qwen-image 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 6 tools
Three generation tools (text_to_image, remix_image, edit_image) share nearly identical descriptions, differing only in a parenthetical mode label, making it hard to distinguish when to use each. get_task, check_pricing, and login are clearly distinct.
All names use snake_case, but most follow a verb_noun pattern while 'login' is a bare verb, creating a minor inconsistency.
Six tools is well-scoped for an image generation API wrapper: three generation modes, task status, pricing, and authentication. Each tool serves a clear purpose without redundancy.
Core workflows (create task, poll status, authenticate, check pricing) are covered, but lifecycle operations like listing tasks or canceling a running task are missing.