mcp -devops

This MCP server implements a suite of DevOps oriented tools and prompts for Ezone, exposing a single MCP endpoint at /mcp. It provides 11 tools for projects, repositories, pipelines and registry management, along with 7 prompts to guide usage, and 14 API document resources. After starting the server, clients such as Cursor or Cherry Studio can send MCP-style requests to retrieve project lists, fetch pipeline details, query repositories, or manage pipelines and images through the defined tool names. The server supports streamable HTTP communication and is designed to integrate with multiple programming clients via MCP.

To use the capabilities, connect to the MCP endpoint and invoke the specific tool names (for example list_projects, list_pipelines, or create_pipeline) supported by the server. You can also leverage the prompts to discover best-practice workflows, such as pipeline lifecycle guidance or API docs queries. Ensure the client passes the required authentication context through MCP requests as described in the AUTH documentation referenced by the project.

Prerequisites:

• Java JDK 17+ (for local builds) or Docker for containerized deployment
• Maven 3.6+ (if building from source)
• Docker (for the recommended containerized run)

Option A: Docker deployment (recommended)

1. Install Docker on your host.
2. Start the server using the predefined image: docker run -d -p 8080:8080 -e SPRING_PROFILES_ACTIVE=prod cleanarch/mcp-server-devops:1.0.0
3. Verify the service is up: curl http://localhost:8080/mcp

Option B: Build from source and run locally

1. Clone the repository: git clone https://github.com/li7hai26/mcp-server-devops.git cd mcp-server-devops
2. Build the project: mvn clean package
3. Run the application (Spring Boot): mvn spring-boot:run The MCP endpoint will typically be http://localhost:8080/mcp

Option C: Binary release or Docker tar (alternate methods)

• Follow the provided release packaging instructions in the README to use the binary or docker tar releases and the included start/stop scripts.

Environment variables and configuration:

• SPRING_PROFILES_ACTIVE controls the running profile (dev, test, prod).
• EZONE API configuration can be provided via environment variables (EZONE_BASE_URL, EZONE_ACCESS_TOKEN, EZONE_COMPANY_NAME, EZONE_TIMEOUT) or via application.yml, but note that in production the MCP client should pass authentication context through HTTP headers.
• The server exposes the MCP endpoint at /mcp and includes a health check pathway at the same location.
• When using Docker, ensure the container has access to the necessary network and that port 8080 is open on the host if you modify defaults.

Common issues:

• If authentication tokens are rejected, verify the client sends credentials per AUTH.md guidelines.
• If logs show startup errors, confirm Java version and that the correct profile is active (prod recommended for production).
• For API docs, refer to docs-api/ in the repository for the latest index and specific resource docs.