MCP server exposing Spinnaker CD platform via Gate API for pipeline and deployment management
A bridge that exposes any Spinnaker instance as an MCP v1 server via the Gate API, written in Go. Category | Tool | Description | ----------|------|-------------| Applications | | List all Spinnaker applications | | | Get detailed application info (accounts, clusters, attributes) | Pipelines | | List pipeline configurations for an application | | | Get a specific pipeline's full configuration | |…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 2 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
A bridge that exposes any Spinnaker instance as an MCP v1 server via the Gate API, written in Go. Category | Tool | Description | ----------|------|-------------| Applications | | List all Spinnaker applications | | | Get detailed application info (accounts, clusters, attributes) | Pipelines | | List pipeline configurations for an application | | | Get a specific pipeline's full configuration | | | Trigger a pipeline with optional parameters | | | Save/create a pipeline definition | | | Update…
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.