go

This MCP server provides a set of Go-focused static analysis and project-scoped tools to help an editor or IDE understand and navigate a Go codebase through the Model Context Protocol. When running in standard I/O mode, the server communicates over stdio with the client (for example, a VS Code extension). It also supports an optional HTTP server mode by providing an address, enabling you to interact with the MCP server over HTTP/JSON. Core capabilities include inspecting the current module, listing package details and exported symbols, enumerating standard library packages and their symbols, and auditing module requirements and project-defined packages. Tools available include: get_go_env (exposes GOROOT, GOBIN, and Go version), list_package_details (details and exported symbols for a given package in the current module), list_stdlib_packages_symbols (symbols for all standard library packages), list_stdlib_packages (documentation for standard library packages), fetch_project_build_required_modules (modules and versions used by the build, respecting go.mod directives), list_project_defined_packages (packages defined by the current project), check_package_exists, and check_package_symbol_exists. Use these tools to analyze your codebase, verify symbol availability, and understand dependencies and package structure, enabling the LLM or tooling to reason about your Go project with up-to-date information.

Prerequisites:

• Go 1.25 or higher (as required by this server).
• Internet access to fetch modules and install the MCP server.

Installation steps:

1. Ensure Go is installed and in your PATH:
   • On macOS/Linux: go version
   • On Windows: go version
2. Install the MCP server binary:
   • go install github.com/xieyuschen/go-mcp-server/mcpgo@latest This places the mcpgo binary in your GOPATH/bin or GOBIN directory, which should be in your PATH.
3. Verify installation:
   • mcpgo --version
4. Run the MCP server (stdio by default). Optionally, run an HTTP server by providing an address flag (see usage notes):
   • mcpgo
   • Or with an HTTP address (if supported by your build): mcpgo -addr :8080

Notes:

• The server is intended to work as an MCP backend for editors like VS Code extensions or other tooling that supports MCP over stdio or HTTP.
• If you opt to run the HTTP server, ensure the chosen port is available and not blocked by a firewall.

Tips and common considerations:

• The server requires Go 1.25+; using older Go versions may lead to build or runtime issues.
• When using the HTTP server mode, provide a valid address/port so clients can connect. The exact flag for enabling HTTP mode may vary; consult the binary's help output (e.g., mcpgo --help) for the exact syntax.
• Use fetch_project_build_required_modules to see all modules used by the project, including any replace directives in go.mod.
• If the editor or tooling reports missing symbols, try list_package_details and list_stdlib_packages_symbols to understand what is available in the current module and the standard library.
• Since this project is archived in favor of gopls-mcp, consider migrating workflows to the newer MCP server if you need more capabilities or updated analyses.