godoc-mcp

MCP.Pizza Chef: mrjoshuak

Your coding assistant asks for a package's documentation instead of reading every file, so far less of the conversation is spent on boilerplate. Two read-only tools are on offer: one fetches the write-up for a package, type, function or method, the other lists the packages inside a project. Nothing on disk is created or changed, and no account or key is needed. You do need Go installed, and asking about an outside library will quietly download that library into a temporary folder.

Coding

Use This MCP server To

Ask what a Go package does without opening its files List every package inside an unfamiliar Go project Look up which methods a type offers Read the documentation for a library I just added Show the source for one function instead of the whole file

README

godoc-mcp

Go Report Card Go Reference License

Overview

godoc-mcp is a Model Context Protocol (MCP) server that provides efficient access to Go documentation. It helps LLMs understand Go projects by providing direct access to package documentation without needing to read entire source files. godoc-mcp can vastly improve the performance of using LLMs to develop in Go by substantially reducing the number of tokens needed to understand and make use of Go packages.

Getting Started

go install github.com/mrjoshuak/godoc-mcp@latest

Why Use godoc-mcp?

In a sentence: godoc-mcp provides a more token efficient way for LLMs to understand Go projects.

Traditional file-reading approaches require LLMs to process entire source files often many files to understand a single package. godoc-mcp provides several advantages:

  1. Token Efficiency: Returns only the essential documentation, reducing token usage significantly
  2. Structured Information: Provides official package documentation in a consistent, well-structured format
  3. Project Navigation: Smart handling of project structures helps LLMs understand multi-package projects
  4. Integration Ready: Works alongside other MCP servers, enabling both high-level and detailed code analysis
  5. Performance: Caching and optimized token usage make godoc-mcp a fast and efficient tool for Go development
  6. Local: Does not require an internet connection to access documentation

With godoc-mcp, a LLM can get precisely the information it needs without having to read entire source files. Here are the different levels of detail that an LLM can get.

  • Documentation for one exported symbol
  • The complete source for one symbol
  • A list of all exported symbols (the concise documentation)
  • A list of all symbols including unexported symbols
  • The full documentation for a package
  • The entire source for a package

This makes godoc-mcp an essential tool for Go developers using LLMs by enabling LLMs to understand significantly more, and in more detail, about the context than previously possible in any programming language.

godoc-mcp FAQ

Do I need an account or a key?
No. It runs entirely on your own machine against the Go tools already installed there, and it works without an internet connection for local code.
Can it change or delete my code?
No. Both tools are marked read-only and only read documentation. The one thing it writes is a throwaway folder it cleans up itself.
What do I need installed first?
Go. If you would rather not install it, there is a ready-made container image you can point your assistant at instead.
Can I use this to understand a project I did not write?
Yes. Point it at the project folder and ask what packages it contains and what each one does.
How many tools does it add?
Two — one for documentation, one for listing packages.
Does it work for other programming languages?
No. It is Go only.
Which apps does it work in?
Claude Desktop and Claude Code have documented one-line setups, and it also speaks the web-based connection styles other assistants use.
Will it reach out to the internet?
Only when you ask about a library that is not already on your machine, in which case it downloads that library before reading its documentation.