mcp

This MCP server provides tooling to help AI assistants understand and work with GoReleaser configurations. It validates GoReleaser config files, surfaces deprecation notices with guided fixes, and lets you access embedded GoReleaser documentation directly through the MCP interface. Use it to ensure your GoReleaser configs are up to date, catch common misconfigurations, and get suggested modernization steps via the update_config prompt. The server exposes a goreleaser-mcp tool that communicates over standard input/output, so it can be integrated into CI pipelines or local tooling that speaks the MCP protocol.

Prerequisites:

• A supported environment (macOS, Linux, or Windows) with a working Node.js/npm or system package manager access as shown below.

Installation steps:

1. npm (recommended):
   • Install globally: npm install -g @goreleaser/mcp
2. macOS (Homebrew):
   • brew install --cask goreleaser/tap/mcp
3. Windows (Winget):
   • winget install goreleaser.mcp
4. Verify installation:
   • goreleaser-mcp --version

Running the MCP server:

• After installation, run the binary directly (it serves via stdin/stdout according to MCP expectations): goreleaser-mcp

If you want to integrate into an automation workflow, reference the mcp_config described in this document to start the goreleaser MCP server as part of your tooling.

Tips and common issues:

• Ensure the goreleaser-mcp binary is in your PATH after installation.
• Use the provided mcp_config to register the server under your MCP orchestrator with the correct command and empty args (the tool runs with standard IO).
• If you upgrade GoReleaser, re-check the MCP server for updated validation rules or new documentation embedding.
• When using in CI, consider pinning the version of the goreleaser-mcp binary to avoid breaking changes.
• If you encounter communication issues, verify that the MCP client and goreleaser-mcp are aligned on the expected protocol (stdio) and that no other process is binding the same resources.