GoReleaser configurations rot quietly — options get deprecated and the build keeps working until it does not. Flagging them is half the job; the part that saves time is the instruction for each one. Embedding the documentation matters for the same reason: an assistant asked about a GoReleaser field is otherwise answering from training data that may predate the version you run.
The official GoReleaser MCP server. It checks a configuration for errors and deprecations, and embeds the GoReleaser documentation so an assistant answers from the real reference rather than from memory.
- Configuration validation that reports errors and deprecated options
- Detailed instructions for fixing each deprecation, rather than only flagging it
- GoReleaser's documentation embedded in the server — including the CI integrations, signing, SBOM, monorepo and verification pages
- An update_config prompt that walks a configuration up to current conventions
Install with `npm install -g @goreleaser/mcp`, `brew install --cask goreleaser/tap/mcp`, or `winget install goreleaser.mcp`. The client runs the goreleaser-mcp command over stdio. Nothing to authenticate.
One command — npm install -g @goreleaser/mcp