Skip to content
MCP server

Spinnaker

Let an assistant inspect and operate Spinnaker pipelines through the Gate API

Runs locallyStatus and history
Install
Pricing
Open source
Platforms
CLI, Linux, macOS
Runs
Locally
Version
0.4.1
Listing updated
2 days ago

About Spinnaker

Spinnaker is an open-source MCP server for developer tools. It runs locally on your machine and is started by your AI client.

This is a single Go binary that sits between an MCP client and a Spinnaker Gate API. Instead of opening each execution and stage in Deck one at a time, you can ask which executions of an application failed today, at which stage, and what that stage returned.

The server is read-only by default. Of its 38 tools, only the 27 that read are registered unless TOOLSETS=all is set, which adds the 11 that change things: triggering, judging, saving, updating and deleting pipelines, cancelling, pausing, resuming, restarting stages, and saving or deleting strategies. Most of those are flagged as destructive so clients that honour annotations can ask first. The evaluate_expression tool posts a SpEL expression to Gate but changes nothing.

It also offers 10 resources and 5 prompts for reviewing a pipeline, investigating a failed execution, auditing a pipeline, summarising an application's infrastructure and planning a rollback.

Calls run as whichever Gate identity you configure: bearer token, basic auth, a session cookie stored by spinnaker-mcp login for SSO setups, optionally with an x509 client certificate. Spinnaker's own access rules apply. It runs over stdio or HTTP, ships as npm, Docker, Helm and binaries for Linux, macOS and Windows, and is GPL-3.0-or-later.

Install

Run in a terminal

claude mcp add spinnaker-mcp --env GATE_URL='<GATE_URL>' --env GATE_TOKEN='<GATE_TOKEN>' --env GATE_PASS='<GATE_PASS>' --env GATE_COOKIE='<GATE_COOKIE>' -- npx -y spinnaker-mcp

Add to claude_desktop_config.json

{
  "mcpServers": {
    "spinnaker-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "spinnaker-mcp"
      ],
      "env": {
        "GATE_URL": "<GATE_URL>",
        "GATE_TOKEN": "<GATE_TOKEN>",
        "GATE_PASS": "<GATE_PASS>",
        "GATE_COOKIE": "<GATE_COOKIE>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "spinnaker-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "spinnaker-mcp"
      ],
      "env": {
        "GATE_URL": "<GATE_URL>",
        "GATE_TOKEN": "<GATE_TOKEN>",
        "GATE_PASS": "<GATE_PASS>",
        "GATE_COOKIE": "<GATE_COOKIE>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "spinnaker-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "spinnaker-mcp"
      ],
      "env": {
        "GATE_URL": "<GATE_URL>",
        "GATE_TOKEN": "<GATE_TOKEN>",
        "GATE_PASS": "<GATE_PASS>",
        "GATE_COOKIE": "<GATE_COOKIE>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "spinnaker-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "spinnaker-mcp"
      ],
      "env": {
        "GATE_URL": "<GATE_URL>",
        "GATE_TOKEN": "<GATE_TOKEN>",
        "GATE_PASS": "<GATE_PASS>",
        "GATE_COOKIE": "<GATE_COOKIE>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "spinnaker-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "spinnaker-mcp"
      ],
      "env": {
        "GATE_URL": "<GATE_URL>",
        "GATE_TOKEN": "<GATE_TOKEN>",
        "GATE_PASS": "<GATE_PASS>",
        "GATE_COOKIE": "<GATE_COOKIE>"
      }
    }
  }
}

Configuration

  • GATE_URLSpinnaker Gate API URL (e.g. https://spin-gate.example.com)Required
  • GATE_TOKENBearer token for Gate
  • GATE_USERBasic auth username (alternative to a token)
  • GATE_PASSBasic auth password
  • GATE_COOKIESESSION cookie of a Gate behind SSO (OAuth2, SAML); or run 'spinnaker-mcp login' once
  • GATE_COOKIE_FILEFile holding that SESSION cookie (default: the file 'spinnaker-mcp login' writes)
  • GATE_CERT_FILEx509 client certificate (PEM); needs GATE_KEY_FILE
  • GATE_KEY_FILEx509 client key (PEM); needs GATE_CERT_FILE
  • GATE_INSECURESkip TLS certificate verification of Gate (testing only)
  • TOOLSETSTool groups to register. Default readonly; 'all' also registers the tools that trigger, cancel, edit, delete and judge pipelines
  • GATE_URLSpinnaker Gate API URL (e.g. https://spin-gate.example.com)Required
  • GATE_TOKENBearer token for Gate
  • GATE_USERBasic auth username (alternative to a token)
  • GATE_PASSBasic auth password
  • GATE_COOKIESESSION cookie of a Gate behind SSO (OAuth2, SAML); or run 'spinnaker-mcp login' once
  • GATE_COOKIE_FILEFile holding that SESSION cookie (default: the file 'spinnaker-mcp login' writes)
  • GATE_CERT_FILEx509 client certificate (PEM); needs GATE_KEY_FILE
  • GATE_KEY_FILEx509 client key (PEM); needs GATE_CERT_FILE
  • GATE_INSECURESkip TLS certificate verification of Gate (testing only)
  • TOOLSETSTool groups to register. Default readonly; 'all' also registers the tools that trigger, cancel, edit, delete and judge pipelines

Tools this server provides (12)

Taken from the project documentation; the running server may differ.

trigger_pipeline
Starts a pipeline run.
judge_stage
Approves or rejects a Manual Judgment stage.
save_pipeline
Saves a pipeline.
update_pipeline
Updates an existing pipeline.
delete_pipeline
Deletes a pipeline.
cancel_execution
Cancels a running execution.
pause_execution
Pauses an execution.
resume_execution
Resumes a paused execution.
restart_stage
Restarts a stage of an execution.
save_strategy
Saves a deployment strategy.
delete_strategy
Deletes a deployment strategy.
evaluate_expression
Sends a SpEL expression to Gate for evaluation; read-only.

What it does

Read-only by default
Only the 27 read tools are registered until toolsets are enabled.
Pipeline and execution control
Optional tools trigger, pause, resume, cancel and restart pipelines and stages.
Infrastructure views
Read server groups, load balancers, clusters, instances, console output and accounts.
Ready-made prompts
Five prompts cover reviewing, investigating, auditing, summarising and rollback planning.
Several auth methods
Bearer token, basic auth, SSO session cookie or x509 client certificate.
Stdio or HTTP
Runs over stdio, or over HTTP bound to localhost unless a token is set.
Many install routes
Available via npm, Docker, Helm or prebuilt binaries.

Good for

  • Find which pipeline stage failed in today's executions
  • See what changed in a pipeline since its last revision
  • Audit pipelines before they run
  • Plan a rollback from an application's infrastructure state
  • Trigger or approve a Manual Judgment from an assistant, when allowed

Pricing

Open source

Free, GPL-3.0-or-later.

Prices change. Check geiserx.github.io before you buy.

Spinnaker FAQ

Can the assistant change my deployments?

Not by default. Set TOOLSETS=all to add the 11 tools that change Spinnaker.

What credentials does it need?

A Gate URL plus a bearer token, basic auth, an SSO session cookie, or an x509 client certificate.

How do I install it?

Run npx -y spinnaker-mcp, or use the Docker image, the Helm chart or a binary.

What licence is it under?

GPL-3.0-or-later.

Is Spinnaker free?

Yes. Spinnaker is open source, so you can use and self-host it for free.

How do I add Spinnaker to Claude Code?

Run this command in your terminal: claude mcp add spinnaker-mcp --env GATE_URL='<GATE_URL>' --env GATE_TOKEN='<GATE_TOKEN>' --env GATE_PASS='<GATE_PASS>' --env GATE_COOKIE='<GATE_COOKIE>' -- npx -y spinnaker-mcp

What are the best alternatives to Spinnaker?

The closest alternatives to Spinnaker are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.

Alternatives to Spinnaker

  1. REA

    MCP server

    CLI and MCP server that lets coding agents reverse engineer apps and binaries

    Runs locally
    • Open source
    • 464K GitHub stars
    • Developer tools
  2. Codebase Memory

    MCP server

    Local MCP server that builds a code knowledge graph for AI coding agents

    Runs locally
    • Open source
    • 48.7K GitHub stars
    • Knowledge and memory
  3. GitHub

    MCP server

    Official MCP server connecting AI assistants to GitHub repos, issues and workflows

    Not checked yet
    • Remote
    • Open source
    • 34.5K GitHub stars
    • Developer tools
  4. MCP toolkit giving coding agents symbol-level code retrieval and editing

    Runs locally
    • Open source
    • 31.5K GitHub stars
    • Developer tools
  5. XERJ

    MCP server

    Local search engine for AI agents with cited answers over your code and docs

    Runs locally
    • Open source
    • 19.2K GitHub stars
    • Knowledge and memory
  6. Ouroboros

    MCP server

    Spec-first layer that pins requirements and verifies results of AI coding agent work

    Runs locally
    • Open source
    • 6.4K GitHub stars
    • Developer tools