About qwen-2-mcp
qwen-2-mcp is a RunAPI MCP server for the Qwen 2 model line, intended for MCP-compatible assistants that need image-generation and editing operations. It also provides task tracking and pricing lookup while keeping access scoped to this model family.
Key features
- 01Create image-generation and editing tasks
- 02Check asynchronous task status and results
- 03Look up model and endpoint pricing
- 04Use multiple Qwen 2 model variants
Use cases
- 01Generate images from text
- 02Edit existing images
- 03Check a submitted task later
- 04Verify pricing before creating a task
MCP support
The MCP server exposes image generation, image editing, task lookup, and pricing tools to compatible clients. Authentication is required for task creation and status checks; pricing lookup does not require sign-in.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @runapi.ai/qwen-2-mcpRUNAPI_API_KEYSecretOptional RunAPI API key for headless hosts. Interactive MCP hosts can use the login tool, which writes shared RunAPI config.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
5Saved tool list · updated 1w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| force | boolean | No | Re-run browser login when the current credential comes from the local config file. |
Details
From the project READMERunAPI Qwen 2 MCP Server
Qwen 2 API access for AI agents: run image generation operations, poll asynchronous results, and check pricing through one focused MCP server.
Works with Claude Code, Codex, Cursor, Windsurf, VS Code, Roo Code, and any MCP-compatible host.
Install | Tools | Models | Agent Prompts | Configuration | Links
Why This Package?
@runapi.ai/qwen-2-mcp is a focused Model Context Protocol server for the Qwen 2 model line on RunAPI.
It gives MCP-compatible assistants direct access to 2 endpoints and 2 model variants without loading the full RunAPI catalog.
Use this per-model server when an agent should stay scoped to Qwen 2. Use @runapi.ai/mcp when one assistant should discover every RunAPI model line.
Install
Add it to Claude Code:
claude mcp add qwen-2 -s user -- npx -y @runapi.ai/qwen-2-mcp
Use project scope when the server should be shared with a repository:
claude mcp add qwen-2 -s project -- npx -y @runapi.ai/qwen-2-mcp
Codex, Cursor, Windsurf, VS Code, Roo Code, and other MCP hosts can use the same stdio command:
{
"mcpServers": {
"qwen-2": {
"command": "npx",
"args": ["-y", "@runapi.ai/qwen-2-mcp"]
}
}
}
check_pricing works before sign-in. For task creation and status polling, ask your assistant to call the login tool. It opens a browser login and saves credentials to ~/.config/runapi/config.json, the same file used by runapi login.
Headless and CI hosts can still set RUNAPI_API_KEY before starting the MCP host.
Ready-made examples are in examples/ for Claude, Cursor, Windsurf, VS Code, and Roo Code.
Tools
| Tool | Auth | Purpose |
|---|---|---|
edit_image | Yes | Create a Qwen 2 edit image task and optionally wait for a terminal status. Returns the task id, status, and output URLs. |
text_to_image | Yes | Create a Qwen 2 text to image task and optionally wait for a terminal status. Returns the task id, status, and output URLs. |
get_task | Yes | Fetch the current status and latest payload for an existing task. |
check_pricing | No | Look up current pricing for a Qwen 2 model and endpoint. |
Models
Qwen 2 covers 2 model variants across 2 endpoints. Each tool accepts the models listed for it:
| Tool | Models |
|---|---|
edit_image | qwen-2-edit-image |
text_to_image | qwen-2-text-to-image |
Model availability can change between releases. Use check_pricing or the Qwen 2 model page for the current catalog view.
Agent Prompts
Ask your assistant in natural language; it can inspect pricing, create the task, and return the task id plus output URLs.
Create a task
Run a Qwen 2 edit image task with RunAPI.
The assistant can call check_pricing, then edit_image, and return the task id, status, and output URLs.
Submit without waiting
Create the task but don't wait for it to finish.
The assistant calls the create tool with wait: false and returns the task id. Check on it later with get_task.
Check pricing before creating
Check current Qwen 2 pricing, then create the task if it matches my request.
The assistant calls check_pricing and can link to the Qwen 2 model page for the canonical catalog entry.
Configuration
The server resolves auth in this order:
RUNAPI_API_KEYenvironment variable, useful for headless and CI hosts~/.config/runapi/config.json, created by the MCPlogintool orrunapi login- No key, which still allows
check_pricing
The config file is normally managed by login. A pre-provisioned headless config can use:
{
"apiKey": "your_runapi_key"
}
Do not commit real API keys.
Links
| Resource | URL |
|---|---|
| Qwen 2 model page | https://runapi.ai/models/qwen-2 |
| npm package | @runapi.ai/qwen-2-mcp |
| GitHub repository | runapi-ai/qwen-2-mcp |
| RunAPI MCP overview | runapi.ai/mcp |
| RunAPI docs | runapi.ai/docs |
License
Licensed under the Apache License, Version 2.0.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.