Server facts
mcp-server
Project
- Author
- OctopusDeploy
- Repository
- github.com/OctopusDeploy/mcp-server
- License
- Not specified
- Category
- Cloud & DevOps
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 101
- Last commit
- Data as of
Tags
- Devops
- mcp server
- octopus deploy
Overview
Deployment troubleshooting begins with Octopus spaces, then narrows to the projects and environments they contain. Deployment queries support filters for project, environment, tenant, channel, and task state, helping separate successful runs from failed or active work. Release tools browse records across a space or within a project and fetch individual releases by ID. Server task lookups provide status, detailed information, and raw details, while process retrieval covers both project deployment processes and frozen versions associated with releases or deployments.
Tenant checks cover individual tenant records, common and project-specific variables, and missing values that can be filtered by tenant, project, or environment. Additional tools inspect project and library variables, deployment targets, certificates, accounts, and Git branches for version-controlled projects. Kubernetes queries return live resource status for a project and environment, with an optional tenant ID for multi-tenant deployments. Setup requires Node.js 20.0.0 or later, an Octopus instance reachable over HTTPS, and an API key. The project remains in Early Access and may introduce breaking changes.
mcp-server setup notes
- mcp-server records stdio only; confirm a network transport upstream before planning remote access.
- mcp-server has no recorded license; confirm reuse terms in its repository.