Octopus Deploy MCP Server
OfficialRelated Servers
Alternatives to Octopus Deploy MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to interact with Azure DevOps entities like projects, repositories, work items, pull requests, and pipelines.4 npm17MIT
- AlicenseBqualityBmaintenanceEnables AI agents to execute read-only DevOps operations including kubectl, terraform, helm, docker, and AWS cost analysis through natural language.11MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Azure DevOps APIs for managing projects, work items, repositories, pull requests, pipelines, and more through natural language.2,823 npmMIT
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to interact with Mender IoT platform for device management, deployment monitoring, and fleet analysis through natural language commands. Provides read-only access to device status, deployment logs, releases, and system monitoring capabilities.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Azure DevOps APIs for managing projects, work items, repositories, pull requests, and pipelines through natural language.12 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Azure DevOps to manage work items, Git repositories, branches, commits, and projects through natural language commands.559 npm5MIT
TDQS
Scored across 30 tools
Most tools target clearly distinct Octopus resources (spaces, projects, deployments, releases, runbooks, tenants, events, etc.). A few adjacent pairs like get_task_from_url vs grep_task_log or get_variables vs get_tenant_variables could cause momentary confusion, but the descriptions generally resolve it.
All names are readable snake_case verb_noun, but read operations are split across list_, find_, get_, and grep_, while writes use create_, deploy_, run_, update_, and execute. There is no single predictable verb pattern, though the names are mostly self-explanatory.
At 30 tools, this exceeds the 25+ threshold for 'too many'. The Octopus domain is broad, but the surface is heavy with niche getters and two generic escape-hatch tools, making it harder for an agent to navigate than a more focused set would be.
Core workflows are covered: explore spaces/projects/environments, create and deploy releases, run runbooks, and inspect tasks/logs. However, many resources are read-only in the curated surface—no create/update/delete for projects, variables, tenants, targets, or certificates—and interruptions can be found but not acted on. The execute tool partially compensates for these gaps.