Octopus Deploy MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OCTOPUS_API_KEY | No | Octopus Deploy API Key (recommended for interactive use). Generate one from your Octopus Deploy user profile. Supplied via environment variable; not accepted on the command line. | |
| 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 flag. | |
| OCTOPUS_ACCESS_TOKEN | No | Short-lived access token (Bearer token) as an alternative to an API key, intended only for automated scenarios. 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 write-tool elicitation confirmation gate 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