SkillFoxx

Octopus Deploy MCP Server

Octopus Deploy MCP Server lets an agent read projects, releases and tasks in Octopus and, once confirmed, deploy releases.

  • 103 ★ on the repository
  • Last commit
  • MPL-2.0
MCP serverOfficial

Broad access

Why this level

  • The agent can create releases, deploy them to environments and run runbooks, production included.
  • The API key grants whatever the Octopus user role allows.
All reasons and checks

octopusdeploy/mcp-serverAuthor:OctopusDeploy

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/octopus-deploy-mcp-server

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • The agent can create releases, deploy them to environments and run runbooks, production included.
  • The API key grants whatever the Octopus user role allows.

This is third-party code. Review the repository files before installing.

What it does

Octopus Deploy MCP Server connects an assistant to your Octopus Deploy instance with an API key or a short-lived access token. The agent browses projects, releases, deployments, tasks, environments and deployment targets and works out why a deployment failed. Tools are grouped into toolsets (`projects`, `deployments`, `releases`, `runbooks`, `tasks`, `tenants`, `kubernetes` and others); enable the ones you need with `--toolsets`. Four tools write: `create_release`, `deploy_release`, `run_runbook` and `update_feature_toggle`. The `--read-only` flag disables every write operation.

Who it is for. Platform and DevOps engineers who ship through Octopus Deploy and want to investigate failed deployments in a conversation with an agent.

Good fit when

  • A deployment failed and the agent must find the task, read its log and name a likely cause.
  • You need an overview of which releases currently run in which environments.
  • The agent creates a release and deploys it to a test environment after you confirm.
  • A feature toggle exists and its rollout percentage is adjusted from chat.

Not a fit when

  • Your Octopus Server is 2026.3 or newer: it has a built-in remote MCP server.
  • The agent role behind the API key cannot be restricted for production deployments.
  • The client has no confirmation prompt and you do not want to pass `confirm: true` in arguments.

Example request

Find the latest failed deployment of the project in the Staging environment, read the task log and explain the cause.

MCP

Transport
stdio
Authentication
API key

Environment variables

OCTOPUS_SERVER_URL required
HTTPS address of the Octopus Deploy instance.
OCTOPUS_API_KEY required, secret
API key from your Octopus profile. Its role decides what the agent can do.
OCTOPUS_ACCESS_TOKEN secret
Short-lived access token for automated scenarios. Takes precedence over the API key.

Limitations

The repository is marked deprecated: the README points to the remote MCP server in Octopus Server 2026.3 and later. Write tools are on by default, so use `--read-only` for production systems. You need Node.js 20 or newer (or Docker) and HTTPS access to the Octopus instance. On Apple Silicon Macs run the Docker image with `--platform linux/amd64`. Some tools need a recent Octopus Server; `--list-tools-by-version` shows which.

How to disable. Remove the `octopusdeploy` entry from the MCP client configuration and revoke the API key you used in your Octopus profile.

FAQ

How do I stop the agent from deploying?

Add the `--read-only` flag: write tools are disabled and `execute` stops passing POST, PUT, PATCH and DELETE.

How are write calls confirmed?

Clients with elicitation support show a confirmation prompt. Others must pass `confirm: true` in the arguments, otherwise the call aborts.

How do I supply the key?

Only through the `OCTOPUS_API_KEY` or `OCTOPUS_ACCESS_TOKEN` environment variables. The server does not take keys as command-line arguments so they stay out of the process list.

Which Octopus Server versions are supported?

Most tools use stable APIs available since version 2021.1. Newer tools state their minimum version in the documentation.

Is the repository still current?

No, it is deprecated. For Octopus Server 2026.3 and newer use the remote MCP server from the Octopus documentation.

Discussion

No questions or reviews yet.

MCP servers

Dokploy MCP

Dokploy MCP Server

Official

The official Dokploy MCP gives an agent 508 API tools covering projects, applications, databases, Docker and backups.

MCP serverBroad access430

Azure DevOps MCP server

Azure DevOps MCP Server

Official

Official Microsoft MCP server for Azure DevOps: work items, repositories, builds, test plans, and wiki from the agent

MCP serverBroad access2.1K

A community MCP server for Azure DevOps work items, code and builds, with PAT authentication for on-premises Azure DevOps Server

MCP serverBroad access400
Official

The official Alibaba Cloud MCP server manages ECS, RDS, OSS and VPC, reads metrics and deploys an app to ECS from an agent.

MCP serverBroad access137

MCP server for Kubernetes: the agent reads cluster state, diagnoses pod failures and runs operations through kubectl

MCP serverBroad access972
Official

Google's MCP server for deploying apps to Cloud Run from an agent, with service listing and log reading

MCP serverBroad access639

README in short

Install through Docker or Node with the key supplied only through environment variables. `--read-only` is recommended for production, and tool groups are enabled with `--toolsets`.

README badge

Report a problem