Qwen 2 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | Yes | Your RunAPI API 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. |
| edit_imageB | Create a Qwen 2 task on RunAPI (edit image). Returns a task id, status, and output URLs. |
| text_to_imageB | Create a Qwen 2 task on RunAPI (text to image). Returns a task id, status, and output URLs. |
| get_taskB | Fetch the current status and latest result payload for a qwen-2 task. |
| check_pricingC | Look up RunAPI pricing for the qwen-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
edit_image and text_to_image both 'create a Qwen 2 task' but their names and descriptions clearly separate the two modes; check_pricing, login, and get_task serve distinct purposes. Slight residual overlap in task-creation semantics but overall clear.
check_pricing, edit_image, text_to_image, and get_task follow a clean verb_noun snake_case pattern. Only 'login' is a bare verb, a minor deviation.
Five tools is well-scoped for a single-model API wrapper covering auth, pricing, generation, editing, and status. Each tool earns its place with no redundancy.
Core lifecycle is covered: authenticate, check pricing, create tasks, and poll status. Minor gaps exist (no list-tasks or cancel-task operation), but agents can work around this with task ids.