RunAPI MCP server for Qwen 2: create tasks, poll status, check pricing.
io.github.runapi-builder/qwen-2-mcp — Qwen 2 MCP Server
RunAPI MCP server for Qwen 2 that exposes operations to create tasks, poll asynchronous results for status, and check pricing through a focused Model Context Protocol server. It is intended for MCP-compatible hosts such as Claude Code, Codex, Cursor, Windsurf, VS Code, and Roo Code.
🛠️ Key Features
Create tasks for Qwen 2 operations
Poll status of asynchronous results
Check pricing
MCP-compatible server for model operations
🚀 Use Cases
Asynchronous AI agent workflows needing status polling
Tooling that requires price lookup for Qwen 2 usage
Integration in editors and agent hosts supporting MCP
⚡ Developer Benefits
Single MCP server interface for Qwen 2 tasks, status polling, and pricing
Works with multiple MCP-compatible environments listed in the source
⚠️ Limitations
The provided description does not specify supported input parameters, authentication details, or tool counts.
@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:
bash
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:
bash
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:
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
text
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
text
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
text
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_KEY environment variable, useful for headless and CI hosts
~/.config/runapi/config.json, created by the MCP login tool or runapi login
No key, which still allows check_pricing
The config file is normally managed by login. A pre-provisioned headless config can use:
