Skip to main content
Glama
OctopusDeploy

Octopus Deploy MCP Server

Official

Deploy a release to environments in Octopus Deploy

deploy_release
Destructive

Deploy a release to one or more environments in Octopus Deploy, supporting both tenanted and untenanted deployments with automatic type detection.

Instructions

Deploy a release to one or more environments in Octopus Deploy

This tool supports both tenanted and untenanted deployments:

  • Untenanted: Don't provide tenants or tenantTags. Can deploy to multiple environments at once.

  • Tenanted: Provide tenants or tenantTags. Can only deploy to ONE environment, but can target multiple tenants.

The tool automatically determines which deployment type to use based on the parameters provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spaceNameYesThe space name
projectNameYesThe project name
releaseVersionYesThe release version to deploy (e.g., '1.0.0')
environmentNamesYesArray of environment names. For tenanted deployments, must contain exactly one environment.
tenantsNoArray of tenant names for tenanted deployment (optional)
tenantTagsNoArray of tenant tags for tenanted deployment (e.g., ['Region/US-West', 'Tier/Production'])
forcePackageRedeploymentNoForce redeployment of packages
updateVariableSnapshotNoUpdate the variable snapshot
forcePackageDownloadNoForce package download
specificMachineNamesNoDeploy to specific machines only
excludedMachineNamesNoExclude specific machines from deployment
skipStepNamesNoSkip specific deployment steps
useGuidedFailureNoUse guided failure mode
runAtNoSchedule deployment for later (ISO 8601 date string)
noRunAfterNoDon't run deployment after this time (ISO 8601 date string)
variablesNoPrompted variable values as key-value pairs
deploymentFreezeOverrideReasonNoReason for overriding deployment freeze
deploymentFreezeNamesNoNames of deployment freezes to override
confirmNoRequired only when the MCP client does not support elicitation. Set to true to confirm deployment; otherwise the tool aborts.
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate destructiveHint: true; description confirms destructive action. Goes beyond annotations by explaining the tenanted/untenanted logic, which is a key behavioral trait.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise, uses bullet points for clarity, front-loaded with main action. Every sentence adds value with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers core logic and decision points for 19 parameters. No output schema, but description focuses on usage rules. Lacks some detail on parameter effects, but schema covers those.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

100% schema coverage provides baseline of 3. Description adds value by explaining how parameters interact (tenants/environmentNames for mode determination), which is not in individual param descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Deploy') and resource ('release to one or more environments'). It differentiates from sibling tools like create_release (creates releases) and run_runbook (runbooks vs releases).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly explains when to use tenanted vs untenanted deployments with clear rules about tenants and environment count. Does not mention alternatives or when not to use this tool, but the guidance is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OctopusDeploy/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server