get_package_doc
Retrieves comprehensive documentation for a Go package, with optional version support.
LABSCO SUMMARY
Go docs as they are today, not as the model remembers them.
A model's picture of a fast-moving Go package is often a release or two behind. These six tools read the current signature, type, examples or version list straight from pkg.go.dev, or at the exact version you name. It is still marked as in development, and pkg.go.dev's rate limits are the practical ceiling.
What it is
A Go documentation server that fetches package docs live from pkg.go.dev, with package search and version lookup from the official Go module index. Its README marks it as still in development.
What you get
- get_package_doc — a package's documentation, at a version you name or the latest
- get_function_doc and get_type_doc — one function's signature and docs, or a type with its methods
- search_packages — find Go packages by name or description
- get_package_examples — a package's example code
- get_package_versions — every published version of a module, from the official module index
- Caching, with a fallback to cached data when pkg.go.dev cannot be reached
Requirements
No account or key. Node.js and npm to build a clone (npm install, then npm run build); your client then runs dist/index.js with node. The README warns that pkg.go.dev rate-limits requests aggressively.
Setup effort
Build from source — git clone https://github.com/captjt/godoc-mcp.git
USE CASES
01
Checking a function's current signature before writing the call
Ask for strings.Split or http.HandleFunc and get the signature and documentation as pkg.go.dev shows them today, not as the model remembers them.
02
Working against the version your go.mod pins
List the versions a module has published, then read a type and its methods at the version you actually depend on.
03
Finding a package for the job and seeing it used
Search Go packages by name or description, then pull a candidate's example code before adding it.
6 tools
Listed in project docs. Your client may show a different list.
get_function_doc
Gets detailed documentation for a specific function, with optional version support.
get_type_doc
Retrieves documentation for types and their methods, with optional version support.
search_packages
Searches for Go packages by name or description.
get_package_examples
Retrieves example code for a package, with optional version support.
get_package_versions
Lists all available versions of a Go package from the official module index.
BEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
Node.js and npm, to install and build the clone
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
Clone the repository
TERMINAL
git clone https://github.com/captjt/godoc-mcp.git
cd godoc-mcpInstall dependencies
TERMINAL
npm installBuild the server
TERMINAL
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"godoc": {
"command": "node",
"args": [
"<YOUR_PATH_TO_GODOC_MCP>/dist/index.js"
],
"env": {
"LOG_LEVEL": "info"
}
}
}
}
