This MCP server implementation lets you use Alibaba Cloud's Qwen Max language model through Claude Desktop via the Model Context Protocol (MCP). It offers a reliable Node.js-based integration with the powerful Qwen Max model.
To install Qwen Max MCP Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @66julienmartin/mcp-server-qwen_max --client claude
git clone https://github.com/66julienmartin/mcp-server-qwen-max.git
cd Qwen_Max
npm install
By default, this server uses the Qwen-Max model. The Qwen series offers several commercial models with different capabilities:
Provides the best inference performance, especially for complex and multi-step tasks. Context window: 32,768 tokens
Available versions:
Balanced combination of performance, speed, and cost, ideal for moderately complex tasks. Context window: 131,072 tokens
Available versions:
Fast speed and low cost, suitable for simple tasks.
Available versions:
To modify the model, update the model name in src/index.ts:
// For Qwen-Max (default)
model: "qwen-max"
// For Qwen-Plus
model: "qwen-plus"
// For Qwen-Turbo
model: "qwen-turbo"
For more detailed information about available models, visit the Alibaba Cloud Model Documentation.
Create a .env file in the project root:
DASHSCOPE_API_KEY=your-api-key-here
Update Claude Desktop configuration:
{
"mcpServers": {
"qwen_max": {
"command": "node",
"args": ["/path/to/Qwen_Max/build/index.js"],
"env": {
"DASHSCOPE_API_KEY": "your-api-key-here"
}
}
}
}
// Example tool call
{
"name": "qwen_max",
"arguments": {
"prompt": "Your prompt here",
"max_tokens": 8192,
"temperature": 0.7
}
}
The temperature parameter controls the randomness of the model's output:
Recommended temperature settings by task:
The server provides detailed error messages for common issues:
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "qwen_max" '{"command":"node","args":["/path/to/Qwen_Max/build/index.js"],"env":{"DASHSCOPE_API_KEY":"your-api-key-here"}}'See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:
{
"mcpServers": {
"qwen_max": {
"command": "node",
"args": [
"/path/to/Qwen_Max/build/index.js"
],
"env": {
"DASHSCOPE_API_KEY": "your-api-key-here"
}
}
}
}To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.json2. Add this to your configuration file:
{
"mcpServers": {
"qwen_max": {
"command": "node",
"args": [
"/path/to/Qwen_Max/build/index.js"
],
"env": {
"DASHSCOPE_API_KEY": "your-api-key-here"
}
}
}
}3. Restart Claude Desktop for the changes to take effect