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_pricingA | 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
Each tool has a clearly distinct purpose: login (auth), edit_image and text_to_image (different task creation modes), get_task (retrieval), and check_pricing (billing). No overlap or ambiguity between tools.
Most tools follow a verb_noun pattern (edit_image, get_task, check_pricing), but login is a bare verb and text_to_image is a noun phrase rather than a clear verb_noun. Slight inconsistency but still readable and predictable.
Five tools cover the essential workflows for a Qwen 2 image server: authentication, two generation modes, result retrieval, and pricing. The count is well-scoped and each tool earns its place.
The tool set covers the full lifecycle: authenticate, create a task (edit or generate), check results, and even check pricing. There are no obvious dead ends or critical missing operations for the stated domain.