GraphPilot
Give coding agents structural memory—callers, callees, blast radius, and symbols—over MCP while you refactor or extend a codebase.
Overview
GraphPilot is a MCP server for the Build phase that provides coding agents structural memory—callers, callees, blast radius, and symbols—for an indexed repository.
What is this MCP server?
- Callers, callees, blast-radius, and symbol queries for the indexed repo
- npm @graphpilot-oss/graphpilot with mcp subcommand (v1.0.1)
- GRAPHPILOT_ROOT optional—falls back to workspace or parent-directory walk
- stdio MCP aimed at structural memory, not generic web search
- Server version 1.0.1
- Package: @graphpilot-oss/graphpilot on npm
- Subcommand: mcp
Community signal: 8 GitHub stars.
What problem does it solve?
Agents miss cross-file impact because they only see snippets, not how functions and modules actually connect.
Who is it for?
Solo developers on one primary codebase who want cheaper, repeatable structural queries inside the agent instead of manual ripgrep archaeology.
Skip if: Greenfield repos with almost no code yet, or teams that need runtime production traces instead of static structure.
What do I get? / Deliverables
After GraphPilot indexes your repo over MCP, refactor and feature prompts can cite caller/callee and blast-radius facts from a maintained graph.
- Agent-accessible caller/callee and symbol graph for the repo
- Blast-radius answers for change planning during build
- Repeatable structural queries without custom AST scripting
Recommended MCP Servers
Journey fit
Build-phase agent work breaks when the model cannot see dependency structure beyond open files. Agent-tooling is the canonical shelf for MCP servers that augment context with repo-native graphs rather than one-off grep prompts.
How it compares
Repo graph MCP server, not a brainstorming or deployment skill.
Common Questions / FAQ
Who is GraphPilot for?
Indie builders and small teams who want MCP-backed code structure—symbols, callers, callees, blast radius—for daily agent-assisted development.
When should I use GraphPilot?
Use it during build/agent-tooling when planning or executing refactors and features that depend on knowing dependency impact across the repo.
How do I add GraphPilot to my agent?
Run @graphpilot-oss/graphpilot with the mcp subcommand via stdio, set GRAPHPILOT_ROOT to your repo path if needed, and register the server in your MCP client.