Summary
One tool, and its input is a file path rather than a package name — it answers for what the code in front of you imports.
Taking a filePath is an unusual shape for a documentation lookup, and it decides the natural use: the question being answered is what this file depends on, rather than what a package you already named does. The model parameter means the summarising is not fixed by the server. Past that, the tool list is a single line with nothing to triangulate against, so the details that would normally matter — module resolution, versions, what happens when the file imports something unpublished — are simply not documented here.
What it is
A single-tool Go documentation lookup that reads GoDoc for the packages behind a given file.
What you get
- One call: godoc takes a filePath and a model and returns Go package information drawn from GoDoc.
Requirements
No credentials are configured on the server.
Setup effort
One command — npx -y godoc-mcp