Octopus Deploy Official MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OCTOPUS_API_KEY | No | Your Octopus Deploy API key. Credentials must be supplied via environment variables (not command-line arguments) to avoid exposing them in the host process list. Recommended for interactive use. | |
| OCTOPUS_SERVER_URL | No | The URL of your Octopus Deploy instance, e.g. https://your-octopus.com. May also be supplied via the --server-url command-line flag. | https://your-octopus.com |
| OCTOPUS_ACCESS_TOKEN | No | A short-lived access token (Bearer token) used as an alternative to an API key. Intended only for automated scenarios such as CI/CD pipelines or machine-to-machine workflows. If both an API key and an access token are provided, the access token takes precedence. | |
| OCTOPUS_SKIP_ELICITATION | No | Set to "true" to bypass the MCP elicitation confirmation gate for write tools entirely. Intended for unattended automation. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityActive
ResponsivenessNo issues