Alibaba Cloud DashScope — Qwen

io.github.nirholas由 GitHub 帳號 nirholas 發布v0.1.4更新於 Oct 24, 2026

Alibaba Cloud DashScope MCP: Qwen chat, embeddings, and model discovery on your own account.

發布方自己的服務：Scope (AEC) - Preview

已驗證STDIO僅桌面知識與記憶 AI 與機器學習

服務詳細資訊

識別碼: io.github.nirholas/alibaba-cloud
傳輸: STDIO
執行環境: Desktop only
信任: Verified
發布於: Sep 16, 2026

安全提示

MCP 服務會接收對話中的工具呼叫請求，並可能執行外部操作。啟用前請先了解該服務能做什麼，並只授予它所需的權限。

註冊中心已驗證此條目所屬的 GitHub 帳號 nirholas。這並不表明該帳號就是產品方。

SourceWeft 的檢查只涵蓋條目是否完整、端點是否回應；不審查伺服器的程式碼，也不審查其工具的行為。

在 README 中新增徽章

向讀者展示該 MCP 服務已收錄於 SourceWeft，徽章連結到本頁。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.nirholas%2Falibaba-cloud.svg)](https://sourceweft.com/mcp/io.github.nirholas%2Falibaba-cloud?utm_source=readme&utm_medium=badge)

概覽

AI 產生的概覽

本機 MCP 伺服器，讓助理透過你自己的阿里雲 DashScope 帳號進行 Qwen 對話、文字向量化與模型清單查詢。

可以做什麼: 使用 qwen-max、qwen-plus、qwen-turbo、qwen-long 等 Qwen 模型進行對話補全，並可逐次指定模型。
以 text-embedding-v3 產生文字向量，用於語意搜尋或 RAG。
列出該 DashScope 帳號可用的模型。
可透過匯出的 buildServer() 進入點嵌入自建的宿主程式。
適用情境: 適合想讓 Claude Desktop、Claude Code、Cursor 等桌面 MCP 用戶端直接呼叫 Qwen 模型或 DashScope 向量化，並計入自己阿里雲帳號用量而非經由其他服務商的情境。
執行需求: 透過 npx 以 stdio 方式在本機執行 npm 套件，需要 Node.js 20 或更新版本。需要阿里雲帳號與 DashScope API 金鑰，透過 DASHSCOPE_API_KEY 提供。選用變數可設定預設對話模型、預設向量模型、自訂基礎位址、中國區以及請求逾時。需要能連線至 DashScope 端點的網路。

安裝前請注意

伺服器需要 DASHSCOPE_API_KEY 中的 DashScope API 金鑰，送出用於向量化的提示與文字會傳到阿里雲 DashScope 端點。用量計入你自己的阿里雲帳號，模型選擇會影響費用。此伺服器由社群建置，與阿里雲無隸屬關係。若將 DASHSCOPE_BASE_URL 指向自訂位址，金鑰與資料會傳送到該位址。

安裝

在 SourceWeft 中

開啟儀表板中的 Alibaba Cloud DashScope — Qwen，將其新增到工作區。
為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照儲存庫中的啟動說明。

README

[three.ws]

@three-ws/alibaba-cloud-mcp

MCP server for Alibaba Cloud DashScope, Qwen chat, embeddings, and model discovery on your own account.

[npm] [license] [node] [three.ws]

Install · Quick start · Tools · Models · three.ws

A Model Context Protocol server that exposes Alibaba Cloud's Qwen models, and anything else in your DashScope account, to MCP clients such as Claude Desktop, Claude Code, and Cursor. It talks directly to the DashScope OpenAI-compatible REST API with your own Alibaba Cloud API key: no intermediary backend, no telemetry, no mock data.

Community-built and not affiliated with Alibaba Cloud. Registry name: io.github.nirholas/alibaba-cloud.

Install

Run it directly with npx (no install needed):

Quick start

With Claude Code, one command:

Or add the server to your MCP client config:

json

{  "mcpServers": {    "alibaba-cloud": {      "command": "npx",      "args": ["-y", "@three-ws/alibaba-cloud-mcp"],      "env": {        "DASHSCOPE_API_KEY": "sk-..."      }    }  }}

{  "mcpServers": {    "alibaba-cloud": {      "command": "npx",      "args": ["-y", "@three-ws/alibaba-cloud-mcp"],      "env": {        "DASHSCOPE_API_KEY": "sk-..."      }    }  }}

Requirements

An Alibaba Cloud account
A DashScope API key, navigate to API Keys and create one
Node.js ≥ 20

Tools

Tool	Description
`qwen_chat`	Chat completion with any Qwen model (qwen-max, qwen-plus, qwen-turbo, qwen-long)
`qwen_embed`	Text embeddings via text-embedding-v3 (1024-dim default, up to 2048)
`qwen_list_models`	List all models available on this DashScope account

Models

Model ID	Use
`qwen-max`	Highest quality: complex reasoning, long documents
`qwen-plus`	Balanced performance (default)
`qwen-turbo`	Fastest and cheapest: simple tasks
`qwen-long`	Long context (up to 1M tokens)
`text-embedding-v3`	Embeddings, semantic search, RAG (default)

Environment variables

Variable	Required	Default	Description
`DASHSCOPE_API_KEY`	yes	-	Your DashScope API key
`DASHSCOPE_MODEL_ID`	no	`qwen-plus`	Default chat model
`DASHSCOPE_EMBED_MODEL_ID`	no	`text-embedding-v3`	Default embedding model
`DASHSCOPE_BASE_URL`	no	International endpoint	Custom DashScope endpoint
`DASHSCOPE_REGION`	no	-	Set to `cn` for the China endpoint
`DASHSCOPE_TIMEOUT_MS`	no	`60000`	Request timeout in ms

Inspect

Programmatic use

The package entry point (@three-ws/alibaba-cloud-mcp) exports buildServer(): a fully-registered McpServer with no transport attached, so you can mount the three tools inside a host of your own instead of spawning the binary. It reads DASHSCOPE_API_KEY when called, and registration is otherwise side-effect free. The DashScope client itself is importable from @three-ws/alibaba-cloud-mcp/src/dashscope.js (loadConfig, DashScopeClient, DashScopeError) when you want the REST wrapper without MCP.

// example.mjs: run with: DASHSCOPE_API_KEY=sk-... node example.mjsimport { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';import { buildServer } from '@three-ws/alibaba-cloud-mcp';
const server = buildServer();
// What this server exposes, before connecting anything.for (const [name, tool] of Object.entries(server._registeredTools)) {  console.log(`${name}: ${tool.title}`);}
// Serve it over stdio (what the bin does), or attach any other MCP transport.await server.connect(new StdioServerTransport());

// example.mjs: run with: DASHSCOPE_API_KEY=sk-... node example.mjsimport { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';import { buildServer } from '@three-ws/alibaba-cloud-mcp';
const server = buildServer();
// What this server exposes, before connecting anything.for (const [name, tool] of Object.entries(server._registeredTools)) {  console.log(`${name}: ${tool.title}`);}
// Serve it over stdio (what the bin does), or attach any other MCP transport.await server.connect(new StdioServerTransport());