Octopus Deploy Official MCP Server
by hoffmann166
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. This is the recommended authentication method for interactive use. | |
| OCTOPUS_SERVER_URL | No | The URL of your Octopus Deploy instance (e.g. https://your-octopus.com). May alternatively be supplied via the --server-url flag. | |
| OCTOPUS_ACCESS_TOKEN | No | A short-lived access/Bearer token, intended only for automated scenarios (e.g. CI/CD pipelines). Takes precedence over the API key if both are provided. | |
| OCTOPUS_SKIP_ELICITATION | No | Set to true to bypass the MCP elicitation confirmation gate for write tools entirely (intended for unattended automation). |
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