Qwen MCP Tool

🚀 Qwen MCP Tool

A Model Context Protocol server for seamless integration with the Qwen CLI. This tool empowers AI assistants such as Claude to harness Qwen's robust code analysis and extensive context window capabilities via the MCP protocol.

🚀 Quick Start

The Qwen MCP Tool serves as a Model Context Protocol server, enabling AI assistants like Claude to utilize Qwen's powerful features. To start using it, follow the installation steps below.

✨ Features

• Large Context Windows: Leverage Qwen's substantial token capacity to analyze large files and entire codebases.
• File Analysis: Incorporate file contents into your queries using the @filename or @directory syntax.
• Sandbox Mode: Execute code and run tests securely in isolated environments.
• Multiple Models: Support various Qwen models, including qwen3-coder-plus and qwen3-coder-turbo.
• Flexible Approval Modes: Control tool execution with plan/default/auto-edit/yolo modes.
• MCP Protocol: Seamlessly integrate with MCP-compatible AI assistants.

📦 Installation

Quick Setup (Easiest - Recommended)

Utilize Claude Code's built - in MCP installer:

claude mcp add qwen-cli -- npx -y @jaggerxtrm/qwen-mcp-tool

This single command automates the entire configuration process!

Via Global Install

Install via npm:

npm install -g @jaggerxtrm/qwen-mcp-tool

Then, add it to Claude Code MCP settings (~/.config/claude/mcp_settings.json):

{
  "mcpServers": {
    "qwen-cli": {
      "command": "qwen-mcp-tool"
    }
  }
}

Via npx (Manual Configuration)

Manually configure to use npx without installation:

{
  "mcpServers": {
    "qwen-cli": {
      "command": "npx",
      "args": ["-y", "@jaggerxtrm/qwen-mcp-tool"]
    }
  }
}

From Source (Development)

1. Clone the repository and install dependencies:

git clone <repo-url>
cd qwen-mcp-tool
npm install

2. Build the project:

npm run build

3. Link locally:

npm link

💻 Usage Examples

ask-qwen

The primary tool for interacting with Qwen AI.

Parameters:

• prompt (required): Your question or instruction.
  • Use @filename to include a file's contents.
  • Use @directory to include all files in a directory.
• model (optional): The model to use (e.g., qwen3-coder-plus, qwen3-coder-turbo).
• sandbox (optional): Enable sandbox mode for safe code execution.
• approvalMode (optional): Control tool execution approval.
  • plan: Analyze tool calls without execution.
  • default: Prompt for approval (default behavior).
  • auto-edit: Auto - approve file edits.
  • yolo: Auto - approve all tool calls.
• yolo (optional): A shortcut for approvalMode='yolo'.
• allFiles (optional): Include all files in the current directory as context.
• debug (optional): Enable debug mode.

Examples:

// Analyze a specific file
{
  "prompt": "@src/main.ts Explain what this code does"
}

// Analyze the entire codebase
{
  "prompt": "@src/ Summarize the architecture of this codebase"
}

// Use a specific model with sandbox
{
  "prompt": "Run the test suite and fix any failures",
  "model": "qwen3-coder-plus",
  "sandbox": true,
  "approvalMode": "auto-edit"
}

ping

A simple echo test to verify the connection.

Parameters:

• prompt (optional): The message to echo (defaults to "Pong!").

Help

Display Qwen CLI help information.

Parameters: None

📚 Documentation

Configuration

The tool uses the following default models:

• Primary: qwen3-coder-plus
• Fallback: qwen3-coder-turbo (used when the primary model reaches quota limits)

You can override these by specifying the model parameter in your requests.

Usage with Claude Code

Once installed as an MCP server, you can use it within Claude Code:

Ask Qwen to analyze the authentication system in @src/auth/

Claude will automatically use the ask-qwen tool with the appropriate parameters.

Project Structure

qwen-mcp-tool/
├── src/
│   ├── index.ts              # MCP server entry point
│   ├── constants.ts          # Configuration and constants
│   ├── tools/
│   │   ├── registry.ts       # Tool registration system
│   │   ├── ask-qwen.tool.ts  # Main Qwen interaction tool
│   │   ├── simple-tools.ts   # Utility tools (ping, help)
│   │   └── index.ts          # Tool exports
│   └── utils/
│       ├── commandExecutor.ts # Command execution utility
│       ├── qwenExecutor.ts    # Qwen CLI wrapper
│       └── logger.ts          # Logging utility
├── package.json
├── tsconfig.json
└── README.md

How It Works

1. The MCP server listens for tool calls via stdio transport.
2. When a tool is called, the server validates the arguments using Zod schemas.
3. For ask-qwen, the prompt is passed to the Qwen CLI with appropriate flags.
4. File references (@filename) are handled by Qwen's built - in file processing.
5. Output is captured and returned to the MCP client.
6. If quota limits are reached, the server automatically switches to the turbo model.

Comparison with Gemini MCP Tool

This tool is inspired by gemini-mcp-tool but adapted for Qwen CLI:

Troubleshooting

"Qwen CLI not found"

Ensure that the Qwen CLI is installed and available in your PATH:

npm install -g @qwen/cli
# or follow instructions at https://github.com/QwenLM/qwen-code

"Command timed out"

For very large files or codebases, the analysis may exceed the default 10 - minute timeout. Consider:

• Using .qwenignore to exclude unnecessary files.
• Breaking down large queries into smaller chunks.
• Using approvalMode: "plan" to analyze without execution.

"Invalid tool arguments"

Verify that your arguments match the tool schema. Use the Help tool to view available options.

📄 License

This project is licensed under the MIT license.

Contributing

Contributions are welcome! Feel free to submit issues or pull requests.

Credits

Inspired by gemini-mcp-tool by jamubc. Built for use with Qwen Code.