go-updatesLABSCO SUMMARY
A narrow tool aimed at a specific failure.
Coding agents write Go the way it was written when their training data was assembled, which means hand-rolled helpers where slices and maps now exist. Handing the model a version-scoped changelog is a cheap fix for that. The size warning is real — filter to the package you are working in rather than asking for everything since 1.13.
What it is
A single-purpose reference server carrying Go release information from 1.13 through 1.24 — 12 versions — embedded in the binary. Ask it what changed since the version you are on, optionally narrowed to one standard library package, and it returns structured Markdown covering language features, standard library additions, runtime and toolchain changes, and upgrade guidance.
What you get
go-updates— the one tool, taking a requiredversionbetween "1.13" and "1.24" and an optionalpackageto filter to one standard library package such as net/http, slices, maps or log/slog- Output shaped for a model rather than a human: hierarchical headings, a summary of impact, chronological version sections, and code examples in fenced blocks
- Everything embedded with go:embed, so the server is a single binary with no data files to ship alongside it
Requirements
Nothing — no account, no key. Go, with the documented client entry running go run github.com/tenkoh/recent-go-mcp@latest; go install and registering the binary path works too. It speaks stdio. The author flags two things: the release data was largely written with an LLM's help and may contain mistakes, and the unfiltered output can be too large for some hosts — using the package filter is the practical answer until pagination lands.
Setup effort
One command — go run github.com/tenkoh/recent-go-mcp@latest
USE CASES
01
Modernising code written for an older Go
Ask what changed since the version the code targets and let the assistant apply the newer patterns.
02
Checking one package before using it
Filter the updates to a single standard library package so the answer is short and specific.
03
Planning an upgrade
Read the language, library, runtime and toolchain changes between your version and the current one in a single pass.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
- go on PATH
- Go 1.24.2 or later
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
go run github.com/tenkoh/recent-go-mcp@latestMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"recent-go-mcp": {
"command": "go",
"args": [
"run",
"github.com/tenkoh/recent-go-mcp@latest"
]
}
}
}
