A Model Context Protocol (MCP) server that provides tools for AI, allowing it to interact with the DataWorks Open API through a standardized
Dataworks mcp server connects DataWorks to AI assistants that speak the Model Context Protocol. A Model Context Protocol (MCP) server that provides tools for AI, allowing it to interact with the DataWorks Open API through a standardized interface. This implementation is based on the Aliyun Open API and enables AI agents to perform cloud resources operations seamlessly.
Want a ready-to-use AI experience for DataWorks without manual MCP setup?
The server implements the Model Context Protocol specification to standardize cloud resource interactions for AI agents.
The server is distributed via npm as alibabacloud-dataworks-mcp-server, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
Before the server will start you need to supply 5 environment variables: REGION, ALIBABA_CLOUD_ACCESS_KEY_ID, ALIBABA_CLOUD_ACCESS_KEY_SECRET, TOOL_CATEGORIES, TOOL_NAMES. Keep credentials in your client's env block or a secrets manager rather than committing them.
Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. DataWorks sits in that group. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
{
"mcpServers": {
"alibabacloud-dataworks-mcp-server": {
"command": "npx",
"args": [
"alibabacloud-dataworks-mcp-server"
],
"env": {
"REGION": "your_dataworks_open_api_region_id_here",
"ALIBABA_CLOUD_ACCESS_KEY_ID": "YOUR_ALIBABA_CLOUD_ACCESS_KEY_ID",
"ALIBABA_CLOUD_ACCESS_KEY_SECRET": "YOUR_ALIBABA_CLOUD_ACCESS_KEY_SECRET",
"TOOL_CATEGORIES": "optional_your_tool_categories_here_ex_UTILS",
"TOOL_NAMES": "optional_your_tool_names_here_ex_ListProjects"
},
"disabled": false,
"autoApprove": []
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| REGION | Declared in the maintainer’s client configuration. | Check documentation |
| ALIBABA_CLOUD_ACCESS_KEY_ID | Declared in the maintainer’s client configuration. | Check documentation |
| ALIBABA_CLOUD_ACCESS_KEY_SECRET | Declared in the maintainer’s client configuration. | Check documentation |
| TOOL_CATEGORIES | Declared in the maintainer’s client configuration. | Optional |
| TOOL_NAMES | Declared in the maintainer’s client configuration. | Optional |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.