Godoc MCP Server

godoc-mcp-server is a tool for searching Go language packages and their documentation. It retrieves information from pkg.go.dev and serves as an MCP server for LLMs. It supports local cache, multi - platform distribution, and provides detailed parameter descriptions to optimize the LLM interaction experience.

Developer tools Search tools #Go documentation #Package search #LLM service #Development tool .Go

rating : 2.5 points

downloads : 27

update time : 2025-04-28

What is godoc-mcp-server?

godoc-mcp-server is a tool based on the Model Context Protocol (MCP) used to search for Go language packages and their detailed documentation from pkg.go.dev. It helps developers quickly find the required packages and relevant information, improving development efficiency.

How to use godoc-mcp-server?

Simply run the server and use the client to send requests. The server communicates with the client through standard input and output.

Applicable scenarios

godoc-mcp-server is suitable for developers who need to frequently look up Go language package documentation, especially during project dependency management and code debugging.

Main features

Search for packages from pkg.go.devSupports searching for Go language packages based on keywords or full package names.

Local cacheUses local cache to reduce repeated search operations and improve response speed.

Package import statisticsDisplays information on how many other packages import a certain package.

Package information retrievalProvides detailed information about the package, including version, author, and documentation.

Advantages and limitations

Advantages

Quickly find Go language packages and their documentation

Supports local cache to optimize performance

Easy to integrate into existing workflows

Limitations

Depends on the service availability of pkg.go.dev

Some advanced features are still under development

How to use

Install godoc-mcp-server

It can be installed by downloading pre - compiled binary files or building from source code.

Start the server

After running the server, the client can start sending requests.

Usage examples

Example 1: Search for a packageThe user wants to find a Go language framework named 'gin'.

Example 2: Get package informationThe user knows the package name is 'github.com/gin-gonic/gin' and needs its detailed documentation.

Frequently Asked Questions

How to install godoc-mcp-server?

Does the server support caching?

Related resources

GitHub repository

The official GitHub repository of the project.

pkg.go.dev

Go language package management platform.

🚀 godoc-mcp-server

Search for Go language packages and their documentation on pkg.go.dev and provide the information to the LLM as an MCP server.

🚀 Quick Start

This server searches for Go language packages and their documentation on pkg.go.dev and provides the information to the LLM.

✨ Features

Utilize local cache to avoid repeated searches.
Provide information on how many packages a particular package is imported by.
Plan to obtain package usage examples.
Automatically release for multiple platforms using GitHub Actions.

📦 Installation

You can download the pre - compiled binary from the release page.

Alternatively, you can install from the source code and compile it yourself:

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

💻 Usage Examples

Basic Usage

Simply make requests using your client. It operates on standard input and output.

📚 Documentation

To - Do List

localCache
- [x] Use local cache to avoid repeated searches (suggested by Reddit users).
searchPackage
- [x] Determine how many packages a particular package is imported by.
getPackageInfo
- [ ] Obtain usage examples.
Release
- [x] Use GitHub Actions to release for multiple platforms.

Development Experience

Descriptions are crucial. When describing parameters, you should inform the client how to use the output of one tool to modify the input format of another tool.

For example, the output of searchPackage includes the names of sub - packages but not the package name. Therefore, if you want the LLM to use getPackageInfo to obtain information about a sub - package, I wrote the following description for the packageName parameter:

The name of the package to search for. If you have previously used searchPackages and the user wishes to obtain information about a sub - package, you should combine them. For example, when the user queries mcp, it returns packageName: github.com/mark3labs/mcp - go/mcp and a sub - package client. Then, if the user wishes to obtain information about the client, you should set packageName to github.com/mark3labs/mcp - go/mcp/client instead of client.

If you use this detailed description, the LLM will tell you the names of some sub - packages. You can directly tell it which package's information to obtain, or which package and its sub - packages' information to obtain, and then it will combine them and call getPackageInfo to retrieve the information.

Therefore, perhaps we should allow users to configure this description to make the tool more useful and efficient.

Library Usage

The Go API exported by this module should currently be considered unstable and may have breaking changes. We may provide stability in the future; please submit issues to feedback your use cases.