spinnaker-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GATE_URL | Yes | Spinnaker Gate API URL | |
| GATE_TOKEN | No | Bearer token for Gate auth |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cancel_executionB | Cancel a running pipeline execution |
| delete_pipelineA | Delete a pipeline configuration from Spinnaker |
| delete_strategyA | Delete a deployment strategy configuration from Spinnaker |
| evaluate_expressionA | Evaluate a SpEL expression against a pipeline execution context |
| find_imagesA | Find images/AMIs available in Spinnaker for a given cloud provider |
| get_accountA | Get details for a specific Spinnaker account |
| get_applicationB | Get detailed information about a Spinnaker application including accounts, clusters, and attributes |
| get_clusterB | Get details for a specific cluster in a Spinnaker application |
| get_console_outputB | Get console output for a specific instance |
| get_executionA | Get the full details of a pipeline execution including stage statuses, outputs, and timing |
| get_firewallB | Get details for a specific firewall rule (security group) |
| get_image_tagsA | Get tags for a Docker image repository in Spinnaker |
| get_instanceA | Get details for a specific instance |
| get_pipelineA | Get the full configuration of a specific pipeline by name |
| get_pipeline_historyA | Get the version history of a pipeline configuration |
| get_scaling_activitiesA | Get scaling activities for a server group in a Spinnaker cluster |
| get_target_server_groupA | Get a target server group in a Spinnaker cluster by selection strategy |
| get_taskA | Get the status and details of a Spinnaker orchestration task (e.g. deploy, resize, rollback) |
| list_accountsA | List all configured Spinnaker accounts (cloud provider integrations) |
| list_applicationsA | List all Spinnaker applications with their metadata |
| list_clustersA | List all clusters for a Spinnaker application |
| list_executionsA | List recent pipeline executions for a Spinnaker application, optionally filtered by status |
| list_firewallsA | List all firewall rules (security groups) across all Spinnaker accounts |
| list_load_balancersA | List all load balancers for a Spinnaker application across all accounts and regions |
| list_networksA | List all networks (VPCs) across all Spinnaker accounts |
| list_pipelinesA | List all pipeline configurations for a Spinnaker application |
| list_server_groupsA | List all server groups (deployment targets) for a Spinnaker application, including instance counts and cloud provider details |
| list_strategiesA | List all deployment strategies configured for a Spinnaker application |
| list_subnetsC | List all subnets for a cloud provider |
| pause_executionA | Pause a running pipeline execution at the current stage |
| restart_stageB | Restart a specific stage within a pipeline execution |
| resume_executionA | Resume a paused pipeline execution |
| save_pipelineB | Save a new pipeline configuration to Spinnaker |
| save_strategyB | Save a new deployment strategy configuration to Spinnaker |
| search_executionsB | Search pipeline executions for an application with optional filters |
| trigger_pipelineB | Trigger a pipeline execution with optional parameters. Returns the execution reference ID. |
| update_pipelineB | Update an existing pipeline configuration in Spinnaker |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 37 tools
Most tools map cleanly to distinct Spinnaker resources, but list_executions and search_executions overlap heavily in purpose, and get_target_server_group/list_server_groups/get_cluster are conceptually close. Descriptions usually clarify intent, but with 37 tools there is real selection risk.
The tool set follows a consistent snake_case verb_noun pattern: list_*, get_*, save_*, delete_*, update_*, cancel_*, pause_*, resume_*, trigger_*. Minor deviations like search_executions, find_images, and evaluate_expression introduce synonym verbs, but the pattern remains predictable overall.
37 tools is heavy and exceeds the 25-tool threshold where most agents struggle to select effectively. While the Spinnaker domain is broad, many of these tools are narrow read-only lookups that could reasonably be consolidated or exposed behind fewer, higher-level operations.
The pipeline/execution lifecycle is well covered: create, update, delete, trigger, pause, resume, cancel, restart, and inspect. However, applications are read-only, strategies lack update/get operations, and there is no way to initiate deployment tasks beyond triggering pipelines, leaving notable CRUD gaps.