io.github.runapi-builder/qwen-2-mcp
RunAPI MCP server for Qwen 2: create tasks, poll status, check pricing.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
@runapi.ai/qwen-2-mcpclaude mcp add qwen-2-mcp -e 'RUNAPI_API_KEY=<your runapi_api_key>' -- npx -y @runapi.ai/qwen-2-mcp@0.2.1
{
"mcpServers": {
"qwen-2-mcp": {
"command": "npx",
"args": [
"-y",
"@runapi.ai/qwen-2-mcp@0.2.1"
],
"env": {
"RUNAPI_API_KEY": "<your runapi_api_key>"
}
}
}
}
Variables d'environnement
RUNAPI_API_KEYsecret Optional RunAPI API key for headless hosts. Interactive MCP hosts can use the login tool, which writes shared RunAPI config.
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
RunAPI 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.
Questions fréquentes
Qu'est-ce que io.github.runapi-builder/qwen-2-mcp ?
RunAPI MCP server for Qwen 2: create tasks, poll status, check pricing.
Comment installer io.github.runapi-builder/qwen-2-mcp ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add qwen-2-mcp -e 'RUNAPI_API_KEY=<your runapi_api_key>' -- npx -y @runapi.ai/qwen-2-mcp@0.2.1. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour io.github.runapi-builder/qwen-2-mcp ?
Oui. Il attend RUNAPI_API_KEY, à renseigner dans sa configuration.
io.github.runapi-builder/qwen-2-mcp est-il open source ?
Oui. Son code est sur GitHub sous licence Apache-2.0.
Qui maintient io.github.runapi-builder/qwen-2-mcp ?
Il est publié par runapi-ai. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.