Salesforce DX MCP Server
salesforcecliLABSCO SUMMARY
Deprecations with the fix attached, not just the warning.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
One command — npm install -g @goreleaser/mcp
USE CASES
01
Finding out why a release configuration misbehaves
Validation names the errors instead of leaving you to bisect the YAML.
02
Bringing an old configuration up to date
Each deprecated option comes with instructions for what replaces it.
03
Asking a question about GoReleaser itself
The documentation ships with the server, so the answer is not from memory.
BEFORE YOU INSTALL
What to know first
Requires
npm on PATH
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"goreleaser": {
"command": "goreleaser-mcp",
"type": "stdio"
}
}
}npm
TERMINAL
npm install -g @goreleaser/mcp
