Summary
Import counts on search results, which is what turns a list of candidates into a decision.
Search for a Go library and you get several plausible packages; the number of packages importing each is the fastest signal for which one the ecosystem actually uses. The docs come back with examples attached, so the model works from the real API rather than from an older version it remembers.
What it is
A Go binary that searches packages on pkg.go.dev and returns their documentation to the model over stdio.
What you get
- searchPackage finds packages, and reports how many other packages import each result
- getPackageInfo returns a package's documentation, including its examples
- Subpackages handled — the search result's subpackage name combines with the parent path to fetch it
- A local cache, so repeated lookups do not re-query every time
Requirements
A compiled binary from the releases page, or go install of the cmd/godoc-mcp-server path. It serves over stdio, so the client just launches it. No account, no key.
Setup effort
One command — go install github.com/yikakia/godoc-mcp-server/cmd/godoc-mcp-server@latest