The Octopus MCP Server provides your AI assistant with powerful tools that allow it to inspect, query, and diagnose problems within your Octopus
The Octopus MCP Server provides your AI assistant with powerful tools that allow it to inspect, query, and diagnose problems within your Octopus instance, transforming it into your ultimate DevOps wingmate. That is what the octopus deploy official mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The server publishes 14 tools. What each one is for:
core — Basic operations (always enabled)projects — Project operationsdeployments — Deployment operationsreleases — Release managementrunbooks — Runbook discovery and executiontasks — Task operationstenants — Multi-tenancy operationskubernetes — Kubernetes operationsmachines — Deployment target operationscertificates — Certificate operationsaccounts — Account operationsinterruptions — Manual intervention and approval operationsInstallation goes through your MCP client rather than a global install: point it at @octopusdeploy/mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Configuration is passed through the environment: OCTOPUS_SERVER_URL, OCTOPUS_API_KEY, OCTOPUS_ACCESS_TOKEN, YOUR_API_KEY, YOUR_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Octopus Deploy Official's toolset — core, projects, deployments and 11 more — is a fair guide to whether it matches your workflow.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| core | Basic operations (always enabled) |
| projects | Project operations |
| deployments | Deployment operations |
| releases | Release management |
| runbooks | Runbook discovery and execution |
| tasks | Task operations |
| tenants | Multi-tenancy operations |
| kubernetes | Kubernetes operations |
| machines | Deployment target operations |
| certificates | Certificate operations |
| accounts | Account operations |
| interruptions | Manual intervention and approval operations |
| featureToggles | Inspect and adjust customer feature toggles |
| context | Authenticated user and project context (current user, Git branches) |
{
"mcpServers": {
"github-com-octopusdeploy": {
"command": "npx",
"args": ["-y", "@octopusdeploy/mcp-server"],
"env": {
"OCTOPUS_SERVER_URL": "your-value",
"OCTOPUS_API_KEY": "your-value",
"OCTOPUS_ACCESS_TOKEN": "your-value",
"YOUR_API_KEY": "your-value",
"YOUR_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| OCTOPUS_SERVER_URL | Endpoint or connection string the server talks to. | Yes |
| OCTOPUS_API_KEY | Credential the server authenticates with. | Yes |
| OCTOPUS_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| YOUR_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_TOKEN | Credential the server authenticates with. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.