Server facts
graphpilot MCP Server
Project
- Author
- graphpilot-oss
- Repository
- github.com/graphpilot-oss/graphpilot
- License
- Not specified
- Category
- Memory & Knowledge
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 17
- Last commit
- Data as of
Tags
- Code Navigation
- Coding Agents
- Local First
- Refactoring
- Static Analysis
- Tree Sitter
- Typescript
- call graph
- code intelligence
- developer tools
- impact analysis
- javascript
- mcp
- model context protocol
- structural memory
Overview
TypeScript and JavaScript code structure is GraphPilot’s focus: it parses repositories with tree-sitter and stores symbols and call relationships in a local graph for coding agents. Through an MCP connection over stdio, gp_recall locates named definitions and returns their locations and signatures, while gp_callers follows incoming or outgoing calls. Results include source anchors with file locations and revision identifiers, giving developers a way to check the evidence behind an agent’s structural answers.
For refactoring and pull-request review, gp_impact traces direct and indirect dependents, identifies potentially affected tests, and reports whether a symbol is part of the public API. Its since parameter narrows analysis to files changed relative to a Git reference. A CLI builds the initial index, watch mode updates it as files change, and gp_index refreshes it after batches of edits. Separate Git worktrees receive separate indexes. Processing stays on the local machine without remote calls or telemetry. The graph covers code relationships rather than arbitrary text, so string literals, configuration values, and unsupported languages remain outside its intended search scope.
graphpilot setup notes
- graphpilot records stdio only; confirm a network transport upstream before planning remote access.
- graphpilot has no recorded license; confirm reuse terms in its repository.