English Français العربية

io.github.runapi-builder/qwen-2-mcp

Official registry Productivity

RunAPI MCP server for Qwen 2: create tasks, poll status, check pricing.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @runapi.ai/qwen-2-mcp
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
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "qwen-2-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "@runapi.ai/qwen-2-mcp@0.2.1"
            ],
            "env": {
                "RUNAPI_API_KEY": "<your runapi_api_key>"
            }
        }
    }
}

Environment variables

  • RUNAPI_API_KEY secret Optional RunAPI API key for headless hosts. Interactive MCP hosts can use the login tool, which writes shared RunAPI config.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. RunAPI Qwen 2 MCP Server
  2. Why This Package?
  3. Install
  4. Tools
  5. Models
  6. Agent Prompts
  7. Configuration
  8. Links
  9. License

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

ToolAuthPurpose
edit_imageYesCreate a Qwen 2 edit image task and optionally wait for a terminal status. Returns the task id, status, and output URLs.
text_to_imageYesCreate a Qwen 2 text to image task and optionally wait for a terminal status. Returns the task id, status, and output URLs.
get_taskYesFetch the current status and latest payload for an existing task.
check_pricingNoLook 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:

ToolModels
edit_imageqwen-2-edit-image
text_to_imageqwen-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:

  1. RUNAPI_API_KEY environment variable, useful for headless and CI hosts
  2. ~/.config/runapi/config.json, created by the MCP login tool or runapi login
  3. 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.

ResourceURL
Qwen 2 model pagehttps://runapi.ai/models/qwen-2
npm package@runapi.ai/qwen-2-mcp
GitHub repositoryrunapi-ai/qwen-2-mcp
RunAPI MCP overviewrunapi.ai/mcp
RunAPI docsrunapi.ai/docs

License

Licensed under the Apache License, Version 2.0.

Frequently asked questions

What is io.github.runapi-builder/qwen-2-mcp?

RunAPI MCP server for Qwen 2: create tasks, poll status, check pricing.

How do I install io.github.runapi-builder/qwen-2-mcp?

It runs on your machine. In 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. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.runapi-builder/qwen-2-mcp need an API key?

Yes. It expects RUNAPI_API_KEY, which you set in its configuration.

Is io.github.runapi-builder/qwen-2-mcp open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Who maintains io.github.runapi-builder/qwen-2-mcp?

It is published by runapi-ai. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.