Octopus 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). Required unless OCTOPUS_ACCESS_TOKEN is supplied. | |
| OCTOPUS_SERVER_URL | No | URL of the Octopus Deploy instance (e.g., https://your-octopus.com). May alternatively be supplied with the --server-url command-line flag. | |
| OCTOPUS_ACCESS_TOKEN | No | Short-lived Octopus access/Bearer token for automated scenarios. If both OCTOPUS_API_KEY and OCTOPUS_ACCESS_TOKEN are supplied, the access token takes precedence. | |
| OCTOPUS_SKIP_ELICITATION | No | Set to true to bypass the MCP elicitation confirmation gate for write tools (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