Octopus Deploy MCP server

What the model can do

Octopus Deploy: which release is deployed to which environment, projects, releases with notes, deployments, deployment and runbook tasks with their outcome and errors, environments, and the audit log of who changed or deployed what. Can create a release, deploy a release to environments or named tenants, cancel, re-run or prioritise a task, replace release notes, record or resolve a release defect, delete a release and create an environment.

Reads

• octopusdeploy_get_dashboardWhat is deployed where: for each project and environment, the release version currently there, whether that deployment succeeded…
• octopusdeploy_list_projectsProjects in the connected space, alphabetically: id (needed by the other tools), name, description and whether disabled.
• octopusdeploy_list_releasesReleases of one project, most recent first: version, when it was created, its channel and release notes.
• octopusdeploy_list_deploymentsDeployments, most recent first: which release of which project went to which environment, when, who started it, whether it hit a failure…
• octopusdeploy_list_tasksServer tasks (deployments, runbook runs, health checks…): state, whether it finished successfully, the error message, when queued…
• octopusdeploy_list_environmentsEnvironments in the connected space, in their deployment order: id (needed to filter deployments and tasks), name…
• octopusdeploy_list_eventsThe audit log, newest first: who did what and when (deployments started, releases created, variables or processes changed, logins…)…

Acts, when you ask

These change something in Octopus Deploy. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• octopusdeploy_create_releaseCreates a release of an Octopus project: a snapshot of its deployment process, variables and package versions.
• octopusdeploy_deploy_releaseDeploys an existing release of an Octopus project to one or more named environments (one deployment each), now or at run_at.
• octopusdeploy_deploy_release_to_tenantsDeploys an existing release of a tenanted Octopus project to named tenants, or to the tenants carrying named tenant tags, in one environment…
• octopusdeploy_cancel_taskCancels a queued or running Octopus server task, such as a deployment or runbook run.
• octopusdeploy_rerun_taskRuns a finished Octopus task again as a new task with the same arguments, for example a runbook run or health check…
• octopusdeploy_prioritize_taskMoves a queued Octopus task to the top of the task queue so it starts next.
• octopusdeploy_update_release_notesReplaces the notes of an Octopus release (Markdown; an empty string clears them).
• octopusdeploy_record_release_defectRecords a defect against an Octopus release, which by lifecycle rules can stop that release being promoted or deployed further.
• octopusdeploy_resolve_release_defectResolves the outstanding defect on an Octopus release, so it can be promoted again.
• octopusdeploy_delete_releasePermanently deletes an Octopus release together with all of its deployments, tasks and other associated records…
• octopusdeploy_create_environmentCreates a deployment environment in the connected Octopus space, placed last in the environment order.

Connect it

First connect Octopus Deploy on Dashboard → Connections, then add Memtro to your client once. The Octopus Deploy tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Octopus Deploy connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which version of the API is in production?
• › What failed to deploy this week, and why?
• › Who deployed to production yesterday?
• › What are the release notes for the latest checkout release?
• › Deploy release 4.13.0 of the Acme portal to Production

Questions

Is this an official Octopus Deploy MCP server?

No. It is Memtro's MCP server with Memtro's Octopus Deploy connector behind it: the connector reads Octopus Deploy through its API with the credentials you connect on Dashboard → Connections, and Octopus Deploy publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Octopus Deploy?

Only when you ask, and only what it has been granted: create a release of a project; deploy a release to one or more named environments, now or at a set time; deploy a release to named tenants or tenant tags in one environment; cancel a queued or running task, such as a deployment; re-run a finished non-deployment task, such as a runbook run; move a queued task to the top of the queue; replace a release's notes; record a defect against a release, which can stop it being promoted; resolve a release's defect; delete a release with its deployments and tasks, permanently; create an environment. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server