godoc-mcp-server

What is godoc-mcp-server?

godoc-mcp-server is an MCP (Model Context Protocol) server that searches Go packages and their documentation from pkg.go.dev, providing the information to an LLM. It is intended for developers using LLMs who need to look up Go package details.

How to use godoc-mcp-server?

Download a compiled binary from the releases page or install from source with go install github.com/yikakia/godoc-mcp-server/cmd/godoc-mcp-server@latest. The server operates on stdio – just use your MCP client to request.

Key features of godoc-mcp-server

• Search for Go packages on pkg.go.dev
• Retrieve detailed package documentation (including examples)
• Support for subpackages (combines parent + subpackage names)
• Local caching to avoid repeated network requests
• Shows the number of other packages that import a given package

Use cases of godoc-mcp-server

• An LLM assistant answering questions about Go standard library or third-party packages
• Searching for packages by name and retrieving their documentation (including subpackages)
• Getting import counts to assess package popularity
• Fetching code examples for a specific package or subpackage

FAQ from godoc-mcp-server

How do I install godoc-mcp-server?

You can download a precompiled binary from the releases page or compile it yourself with go install github.com/yikakia/godoc-mcp-server/cmd/godoc-mcp-server@latest.

What transport does godoc-mcp-server use?

It uses stdio as the transport – no HTTP server or authentication is involved.

How does subpackage handling work?

The server’s searchPackage tool returns subpackage names (without the parent prefix). When the LLM calls getPackageInfo, it should combine the parent package name with the subpackage name (e.g., github.com/mark3labs/mcp-go/mcp/client). The tool description instructs the LLM how to do this.

Does godoc-mcp-server cache results?

Yes, it includes a local cache to avoid fetching the same data from pkg.go.dev on every request.

What data does godoc-mcp-server access?

All data is fetched live from pkg.go.dev; the server does not store data permanently (aside from the optional local cache).