Octopus Deploy MCP integration for AI agents.
Connect AI agents to Octopus Deploy through 12 structured actions, including get current user, get deployment, and get environment. Review authentication, in…
- ACTION CONTRACTS
- 12
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Octopus Deploy integration exposes
The Octopus Deploy Agent App exposes 12 provider-backed actions for developer tools and infrastructure work. Its current contract lets an authorized agent fetch the current octopus deploy user for the connected api key, fetch one deployment inside an octopus deploy space by id, and fetch one environment inside an octopus deploy space by id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Octopus Deploy account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Octopus Deploy capabilities.
Showing 12 of 12 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_current_userREADFetch the current Octopus Deploy user for the connected API key.
get_deploymentREADFetch one deployment inside an Octopus Deploy space by ID.
INPUTS: spaceIdentifier / id
get_environmentREADFetch one environment inside an Octopus Deploy space by ID.
INPUTS: spaceIdentifier / id
get_projectREADFetch one project inside an Octopus Deploy space by ID.
INPUTS: spaceIdentifier / id
get_releaseREADFetch one release inside an Octopus Deploy space by ID.
INPUTS: spaceIdentifier / id
get_taskREADFetch one Octopus Deploy server task inside a space by ID.
INPUTS: spaceIdentifier / id
list_deploymentsREADList deployments inside an Octopus Deploy space with optional filters.
INPUTS: spaceIdentifier / channels / environments / ids / partialName
list_environmentsREADList environments inside an Octopus Deploy space.
INPUTS: spaceIdentifier / ids / partialName / skip / take
list_projectsREADList projects inside an Octopus Deploy space.
INPUTS: spaceIdentifier / ids / partialName / skip / take
list_releasesREADList releases inside an Octopus Deploy space.
INPUTS: spaceIdentifier / skip / take
list_spacesREADList Octopus Deploy spaces visible to the connected API key.
INPUTS: ids / name / partialName / skip / take
list_tasksREADList Octopus Deploy server tasks inside a space with optional filters.
INPUTS: spaceIdentifier / active / batch / description / environment
INPUT CONTRACTS
Know what the action needs before it runs.
get_deployment
spaceIdentifierREQUIRED- The Octopus Deploy space identifier, ID, or slug.
idREQUIRED- The Octopus Deploy resource ID.
get_environment
spaceIdentifierREQUIRED- The Octopus Deploy space identifier, ID, or slug.
idREQUIRED- The Octopus Deploy resource ID.
get_project
spaceIdentifierREQUIRED- The Octopus Deploy space identifier, ID, or slug.
idREQUIRED- The Octopus Deploy resource ID.
get_release
spaceIdentifierREQUIRED- The Octopus Deploy space identifier, ID, or slug.
idREQUIRED- The Octopus Deploy resource ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Current User
Fetch the current Octopus Deploy user for the connected API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_current_userVerify with Get Deployment
Fetch one deployment inside an Octopus Deploy space by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_deploymentSAFETY BOUNDARY
Operate Octopus Deploy with explicit limits
- Authorize Octopus Deploy with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Octopus Deploy data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Octopus Deploy rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Octopus Deploy task completed successfully.
CONNECTION MODEL
API key
Octopus Deploy API key sent with the X-Octopus-ApiKey header. Create or copy a key from your Octopus Web Portal profile under My API Keys: https://octopus.com/docs/octopus-rest-api/how-to-create-an-api-key.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 12
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Octopus Deploy.