AlibabaCloud DevOps MCP

Implements the Model Context Protocol (MCP) as a standardized interface layer that registers DevOps tools (Codeup, Projex, Flow) and translates AI assistant requests into structured tool invocations. The server uses a tool registry pattern where each tool is defined with JSON schemas and mapped to implementation functions, enabling AI assistants like Cursor and Tongyi Lingma to discover and call DevOps operations through a unified protocol without direct API knowledge.

Exposes Codeup (Alibaba's code management service) operations through MCP tools that enable AI assistants to create/delete branches, read/write files, list repositories, and manage repository metadata. The implementation wraps Yunxiao API calls through the YunxiaoClient, translating high-level repository operations (e.g., 'create_branch') into authenticated HTTP requests with proper error handling and response parsing.

Implements consistent error handling across all tool invocations, translating Yunxiao API errors into structured MCP error responses with context and actionable messages. The error handling layer catches API failures, network errors, and validation errors, formatting them as MCP-compliant error responses that AI assistants can interpret and act upon.

Provides a framework for registering new tools with the MCP server through a declarative tool definition and implementation function mapping. The framework allows developers to add new Yunxiao capabilities by defining tool schemas and implementing handler functions, with the server automatically registering tools during initialization without modifying core server logic.

Provides MCP tools for creating, listing, and managing change requests (merge requests/pull requests) in Codeup, enabling AI assistants to initiate code review workflows, add reviewers, and track review status. The implementation maps change request operations to Yunxiao API endpoints, handling authentication, request formatting, and response parsing to abstract the underlying REST API complexity.

Exposes Codeup's code comparison capabilities through MCP tools that generate diffs between branches, commits, or file versions. The implementation calls Yunxiao's diff API endpoints, returning structured diff data that AI assistants can analyze to understand code changes, identify patterns, or generate review comments without requiring local Git diff operations.

Exposes Projex (Alibaba's project management service) operations through MCP tools for creating, listing, and updating work items (tasks, bugs, features) and managing project metadata. The implementation wraps Projex API calls through YunxiaoClient, translating work item operations into authenticated requests with support for custom fields, status transitions, and assignment workflows.

Provides MCP tools for managing sprints in Projex, including creating sprints, assigning work items to sprints, and tracking sprint progress. The implementation calls Projex sprint APIs to handle sprint lifecycle (planning → active → closed) and work item allocation, enabling AI assistants to optimize sprint planning and capacity management.

Exposes Flow (Alibaba's CI/CD service) operations through MCP tools for listing pipelines, triggering pipeline executions, and monitoring build status. The implementation wraps Flow API calls through YunxiaoClient, translating pipeline operations into authenticated requests with support for parameterized builds and real-time status tracking.

Implements both stdio (standard input/output) and Server-Sent Events (SSE) transport modes for MCP communication, allowing flexible deployment scenarios. The server initialization logic selects transport based on command-line flags, with stdio providing direct process communication for local AI assistants and SSE enabling network-based communication for remote or web-based AI tools.

Provides YunxiaoClient as a centralized HTTP client for all Yunxiao API interactions, handling authentication token management, request formatting, error handling, and response parsing. The client abstracts API endpoint details and authentication complexity, allowing tool implementations to focus on business logic rather than HTTP mechanics.

Defines tools with JSON schemas that describe parameters, return types, and descriptions, enabling AI assistants to understand tool capabilities and constraints without documentation. The schema-based approach uses standard JSON Schema format, allowing AI models to validate inputs and generate appropriate tool calls based on schema constraints.