gograph — Claude Code MCP server for Go analysis
gograph builds a local structural graph of a Go repository so an agent can trace callers and assess the reach of a change. Use it when reviewing a refactor.
Open on GitHubWhat gograph does
gograph runs locally over stdio and maps the structure of a Go repository. An agent can follow call sites and interface implementations, then inspect the likely impact of edits. Its precise mode adds type checking; project code is not executed.
Indexing uses the installed Go toolchain. Precise analysis loads package types, while doc invokes go doc, so these operations follow the configured module, cache, and network policies. A restricted dependency setup can therefore prevent precise analysis. Session data stays in .gograph/sessions/; it is not sent to gograph services.
What it helps with
- trace callers before changing a Go function
- find implementations of an interface across a repository
- assess which code and tests a change may affect
- inspect package relationships without running project code
Example prompts for the agent
- Find every caller of
ParseConfigand describe the impact of changing it. - Trace the implementations of
Storeand list the related files. - Assess how edits to
internal/router/router.gocould affect tests and callers.
How to install gograph
Install
The MCP registry has no launch command for it: see the repository README
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about gograph
How do I install gograph for Claude Code?
Install the CLI with brew install --cask ozgurcd/tap/gograph. This installs gograph; connecting the MCP server in Claude Code is a separate setup step.
What does gograph do?
It builds a local graph of a Go repository so an agent can trace calls, locate interface implementations, and assess the reach of edits. It does not run project code.
What is required for precise Go analysis?
An installed Go toolchain is required. Precise mode loads package types and follows the configured module, cache, and network policies.
