godoc

godoc-mcp-server is an MCP server that indexes Go packages and their documentation from pkg.go.dev and returns structured results suitable for prompting or chaining in an LLM workflow. It operates as a stdio-based service, so you typically start the binary and then issue MCP-formatted requests through its input stream and read responses from its output. Use the server to search for packages, retrieve package information, examples, and related metadata that help explain Go packages and their usage. This server is designed to expose tools like searchPackage and getPackageInfo in a way that can be composed with other MCP tools to build richer LLM prompts and workflows.

To use it, start the godoc-mcp-server binary in your environment. Then send MCP requests over standard input and read the responses from standard output. You can leverage its search capabilities to find Go packages by name or topic, then request detailed information for specific packages or subpackages, including usage examples when available. The goal is to provide the LLM with actionable, structured data that can be formatted for different downstream tasks, such as prompt refinement, documentation synthesis, or code generation guidance.

Prerequisites:

• Go toolchain installed (Go 1.17+ recommended)
• A compatible environment to run binaries (Linux/macOS/Windows with proper executable permissions)

Option A: Install the binary from source (build from GitHub source)

1. Ensure Go is installed and GOPATH is configured
2. Build and install the binary:

go install github.com/yikakia/godoc-mcp-server/cmd/godoc-mcp-server@latest

This places the binary in your Go bin directory (e.g., $GOPATH/bin or $(go env GOPATH)/bin).

Option B: Download prebuilt binary

1. Go to the releases page: https://github.com/yikakia/godoc-mcp-server/releases/tag/latest
2. Download the appropriate binary for your platform and make it executable:

chmod +x godoc-mcp-server

3. Move the binary to a directory in your PATH, e.g.:

mv godoc-mcp-server /usr/local/bin/

Run it via the command shown in the README; since this MCP server runs over stdio, you’ll interact with it through standard input/output streams.

Notes and tips:

• The server runs as a stdio-based service; ensure your client correctly pipes requests and reads responses.
• The README mentions a local cache feature intended to reduce repeated searches; if available, enable or configure it to improve performance.
• When designing prompts for the LLM, be mindful of how searchPackage results may omit certain metadata (e.g., package name when listing subpackages) and plan to combine outputs with getPackageInfo accordingly.
• If you plan to run in containers or CI, consider mounting a cache directory if localCache is supported, or run with a workdir suitable for cache storage.
• Ensure network access to pkg.go.dev for live lookups unless a local cache is configured.
• There is no npm package associated with this server (npm_package: null). The server is a Go binary and is typically invoked directly or via a container/runner that supports stdio MCP communication.