io.github.GeiserX/spinnaker-mcp — Model Context Protocol (MCP) Server

This MCP server exposes the Spinnaker CD platform via the Gate API for pipeline and deployment management. It is identified as io.github.GeiserX/spinnaker-mcp and is associated with Model Context Protocol and MCP server tooling, including a spinnaker-gate integration.

🛠️ Key Features

Integrates Spinnaker continuous delivery (CD) via Gate API
Supports pipeline management
Supports deployment management
Tagged for Kubernetes and infrastructure use (topics include kubernetes, infrastructure, spinnaker-gate)

🚀 Use Cases

Managing Spinnaker pipelines through an MCP-enabled workflow
Controlling and updating deployments using Gate API access
Automating DevOps operations for cloud-native continuous delivery

⚡ Developer Benefits

Developer-facing MCP server for model-context-protocol usage
Aligns with CI/CD and pipeline tooling patterns (ci-cd, pipeline)
Includes language- and platform-oriented topics (go, golang, docker, kubernetes)

⚠️ Limitations

The provided description specifies Gate API exposure for pipeline/deployment management; other Spinnaker capabilities are not described.

spinnaker-mcp

A bridge that exposes any Spinnaker instance as an MCP server via the Gate API, written in Go.

It gives an LLM 37 tools to read and operate Spinnaker: applications, pipelines, executions, strategies and infrastructure.

MCP Inspector connected to spinnaker-mcp started with TOOLSETS=readonly: only read tools are listed, and search_executions is selected with its arguments

Features

Applications and pipelines: list, read, trigger, save, update and delete pipelines, with revision history.

Executions: list, search by trigger type, time range and status, cancel, pause, resume, restart a stage, evaluate SpEL.

Deployment strategies: list, save and delete.

Infrastructure: server groups, load balancers, clusters, firewalls, instances and console output, images, networks, subnets, accounts.

Orchestration task status (deploy, resize, rollback).

Bearer token, basic auth or x509 client certificate against Gate.

stdio or HTTP transport; HTTP binds to 127.0.0.1 by default.

Ships as an npm package (npx spinnaker-mcp), a Docker image and multi-arch Go binaries.

Quick start

Add the server to your MCP client (Claude Code, Claude Desktop, Cursor):

json

{
  "mcpServers": {
    "spinnaker": {
      "command": "npx",
      "args": ["-y", "spinnaker-mcp"],
      "env": { "GATE_URL": "https://spin-gate.example.com", "GATE_TOKEN": "your-token-here" }
    }
  }
}

Needs Node 18 or newer; the npm package runs the Go binary over stdio. Docker, local builds and the other credentials are in Getting started.

Documentation

Getting started: npm, Docker, Helm, local build, and the client configuration

Configuration: every environment variable, the read-only toolset, the HTTP endpoints

Usage: the 37 tools and which ones change Spinnaker, the 10 resources, the 5 prompts

Development: testing, contributing, credits

Related projects: the other MCP servers and the registry listings

Install

Configuration

Environment variables

GATE_URLrequired

Spinnaker Gate API URL (e.g. http://spin-gate:8084)

GATE_TOKENsecret

Bearer token for Gate authentication

GATE_USER

Basic auth username (alternative to token)

GATE_PASSsecret

Basic auth password

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "spinnaker-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "spinnaker-mcp@0.3.2"
      ],
      "env": {
        "GATE_URL": "<YOUR_GATE_URL>",
        "GATE_TOKEN": "<YOUR_GATE_TOKEN>",
        "GATE_USER": "<YOUR_GATE_USER>",
        "GATE_PASS": "<YOUR_GATE_PASS>"
      }
    }
  }
}

io.github.GeiserX/spinnaker-mcp