Octopus Deploy
Introducing remote MCP for Octopus Deploy
Octopus Deploy now includes a built-in remote MCP server, so agents can connect over HTTP to an instance's /mcp endpoint without a local install. The server initially exposes a selected set of core features covering spaces, projects, tenants, deployments, runbooks, task logs, audit events and tenant variables, with access depending on the authentication method and granted permissions. Octopus Cloud customers can use it now and Octopus Server customers will get it in the 2026.3 release. The company says scoped API keys, OAuth for the MCP server, agent-aware policies and an improved audit log are planned for the coming months.
What changes for platform teams
Platform teams running Octopus can connect agents without distributing and updating a local MCP server on every machine. Governance controls such as scoped API keys, agent-aware policies and agent audit filtering are not yet available, so teams should plan access controls before letting agents trigger deployments.
No itemized notes for this release.
Full release notes ↗ · all Octopus Deploy releases
written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules