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());