Introducing remote MCP for Octopus Deploy

Octopus has introduced a built-in remote Model Context Protocol server that lets AI agents connect to an Octopus instance through its `/mcp` HTTP endpoint, eliminating the need to install and maintain a local MCP server on each user’s machine. Initially available to Octopus Cloud customers and planned for Octopus Server 2026.3, the feature supports permission-controlled access to core capabilities including navigating spaces, projects, tenants, and tags; checking deployment and pull request status; creating, deploying, and promoting releases; running runbooks; investigating task failures and configuration issues; and querying audit events and deployment health. Octopus plans to expand the remote MCP’s functionality based on user feedback while developing broader agent-governance features, including scoped API keys, OAuth authentication, agent-aware policies, and enhanced audit-log filtering for agent activity.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.