MCP server that bridges any Spinnaker instance via its Gate API, exposing application management, pipeline operations, and deployment infrastructure
MCP server that bridges any Spinnaker instance via its Gate API, exposing application management, pipeline operations, and deployment infrastructure over JSON-RPC. Exposed over MCP by the spinnaker mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
A bridge that exposes any Spinnaker instance as an MCP v1 server via the Gate API, written in Go.
Everything the assistant can do here goes through one of these:
Category — ToolApplications — list_applicationsPipelines — list_pipelinesExecutions — list_executionsStrategies — list_strategiesInfrastructure — list_server_groupsTasks — get_taskVariable — DefaultGATE_URL — http://localhost:8084GATE_TOKEN — (empty)GATE_USER — (empty)GATE_PASS — (empty)spinnaker-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 2 environment variables: GATE_URL, GATE_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Spinnaker MCP's toolset — Category, Applications, Pipelines and 11 more — is a fair guide to whether it matches your workflow. It is maintained by geiserx; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Category | Tool |
| Applications | list_applications |
| Pipelines | list_pipelines |
| Executions | list_executions |
| Strategies | list_strategies |
| Infrastructure | list_server_groups |
| Tasks | get_task |
| Variable | Default |
| GATE_URL | http://localhost:8084 |
| GATE_TOKEN | _(empty)_ |
| GATE_USER | _(empty)_ |
| GATE_PASS | _(empty)_ |
| GATE_CERT_FILE | _(empty)_ |
| GATE_KEY_FILE | _(empty)_ |
{
"mcpServers": {
"spinnaker": {
"command": "npx",
"args": ["-y", "spinnaker-mcp"],
"env": {
"GATE_URL": "https://spin-gate.example.com",
"GATE_TOKEN": "your-token-here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GATE_URL | Endpoint or connection string the server talks to. | Yes |
| GATE_TOKEN | Credential the server authenticates with. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.