Alibaba Cloud DevOps:Alibaba Cloud DevOps MCP Server

Remote hosting (Streamable HTTP)

Replace <YOUR_TOKEN> with your personal access token:

{
  "mcpServers": {
    "yunxiao": {
      "url": "https://openapi-rdc.aliyuncs.com/ai/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

If your client does not support custom headers, you can use a Query String to pass the token instead: https://openapi-rdc.aliyuncs.com/ai/mcp?yunxiao_access_token=<YOUR_TOKEN>.

If your client supports OAuth, you can skip the token and use browser-based authorization instead. For details, see "Advanced configuration > Authentication methods > OAuth 2.0 Authorization" below.

Local (stdio)

{
  "mcpServers": {
    "yunxiao": {
      "command": "npx",
      "args": ["-y", "alibabacloud-devops-mcp-server"],
      "env": {
        "YUNXIAO_ACCESS_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}

Toolset filtering

The Alibaba Cloud DevOps MCP Server provides 194 tools covering 8 categories. Having too many tools can consume significant model context. If you only need certain categories, you can specify toolsets so the server only delivers the corresponding tools (basic tools are always included).

• Remote Hosting mode: Append ?toolsets=... to the URL, or add the request header X-Devops-Toolsets: ....

• stdio mode: Add the command-line argument --toolsets=..., or set the environment variable DEVOPS_TOOLSETS=....

Available values (comma-separated): code-management, organization-management, project-management, pipeline-management, packages-management, application-delivery, test-management. If not specified, all tools are enabled by default.

Remote access example:

{
  "mcpServers": {
    "yunxiao": {
      "url": "https://openapi-rdc.aliyuncs.com/ai/mcp?toolsets=code-management,project-management",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
    }
  }
}

Authentication methods

The Alibaba Cloud DevOps MCP Server supports two types of authentication: manually passing a Personal Access Token (PAT), or using OAuth 2.0 authorization for supported clients to connect without a token.

Using a Personal Access Token (PAT)

The following three methods are available for passing a personal access token, listed by recommended priority:

In stdio mode, pass the token through the YUNXIAO_ACCESS_TOKEN environment variable. The above configurations are not needed.

OAuth 2.0 Authorization

For MCP clients that support OAuth, such as Qoder/QoderCLI and Claude Code, you do not need to create a personal access token in advance. In Remote Hosting mode, after entering the service URL, the client will automatically initiate the OAuth 2.0 authorization code + PKCE flow, opening a browser to guide you through login and authorization, then automatically obtaining and refreshing tokens. This applies to Remote Hosting (Streamable HTTP) access.

When configuring, enter only the service URL without the Authorization header:

{
  "mcpServers": {
    "yunxiao": {
      "url": "https://openapi-rdc.aliyuncs.com/ai/mcp"
    }
  }
}

• Service URL: Central station https://openapi-rdc.aliyuncs.com/ai/mcp; Region station https://<organization-specific-domain>/ai/mcp.

• Endpoint discovery, client registration, and PKCE are all handled automatically by the client. You do not need to manually apply for a client_id or configure a client_secret (the platform uses public clients).

• Access tokens issued after authorization are valid for 24 hours, and refresh tokens for 90 days. The client automatically refreshes tokens. Re-authorization is required after the refresh token expires.

Region configuration (Dedicated Edition)

If you are using an Alibaba Cloud DevOps Region station, each Region independently provides an officially hosted MCP endpoint. The usage is the same as the central station — simply replace the service address with your organization-specific domain.

Method 1: Remote Hosting (Streamable HTTP, recommended, no installation required)

• Service address: https://<organization-specific-domain>/ai/mcp, for example https://your-org.devops.aliyuncs.com/ai/mcp (your regular Alibaba Cloud DevOps Region domain with /ai/mcp appended)

• Authentication: Authorization: Bearer <YOUR_TOKEN> (or X-Yunxiao-Token: <YOUR_TOKEN>). If your client supports OAuth, you can skip the token and use browser-based authorization instead. For details, see "Advanced configuration > Authentication methods > OAuth 2.0 Authorization" above.

{
  "mcpServers": {
    "yunxiao": {
      "url": "https://your-org.devops.aliyuncs.com/ai/mcp",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
    }
  }
}

Method 2: Local (stdio)

Use the YUNXIAO_API_BASE_URL environment variable to point to your Region domain:

{
  "mcpServers": {
    "yunxiao": {
      "command": "npx",
      "args": ["-y", "alibabacloud-devops-mcp-server"],
      "env": {
        "YUNXIAO_ACCESS_TOKEN": "<YOUR_TOKEN>",
        "YUNXIAO_API_BASE_URL": "https://your-org.devops.aliyuncs.com"
      }
    }
  }
}