octopus-deploy

This MCP server provides an integration layer for Octopus Deploy via the MCP protocol. It exposes tools to manage projects, releases, and deployments across different Octopus spaces. You can list projects, inspect individual project details, fetch the latest releases, create new releases, deploy a release to an environment, and monitor deployment status. The server supports multi-space usage, enabling operations across separate Octopus spaces within the same MCP client setup. To run it, you’ll typically provide an Octopus Deploy URL and an API key, which are wired into the Docker container at runtime.

Prerequisites:

• Docker installed and running
• Access to an Octopus Deploy server and a valid API key

Installation steps:

1. Clone the repository: git clone https://github.com/armanzeroeight/octopus-deploy-mcp-server.git cd octopus-deploy-mcp

2. Build the Docker image (as per the repository's guidance): ./scripts/build.sh This will produce a Docker image tagged as octopus-deploy-mcp:latest.

3. Run the MCP server using Docker:

   • You will typically set environment values for your Octopus server URL and API key. For example: docker run --rm -i
     -e OCTOPUS_URL=https://your-octopus-server.com
     -e OCTOPUS_API_KEY=YOUR_API_KEY
     octopus-deploy-mcp:latest
     octopus-deploy-mcp

4. Alternatively, integrate via your MCP client using the provided mcp.json configuration (see README).

Notes:

• The API key should be kept secret and provided securely to the MCP client.
• Ensure the Octopus server URL excludes any /api suffix.

Tips and considerations:

• Ensure the Octopus Deploy URL and API key have the required permissions for the intended space and actions.
• If you encounter errors like "Space 'Default' not found" verify the target space exists and the API key has access to it; the space name is case-sensitive.
• Check Docker daemon status if you see Docker-related build/run failures.
• The included configuration uses Docker to run the MCP server image; tweak the environment variables in your mcp.json as needed for different environments.
• For development, you can test the Docker image locally with the repository's test scripts (e.g., ./scripts/test-docker.sh).
• Debug logs can help diagnose issues; look for verbose logging in the MCP client and the container logs.