Graphpilot

Name: Graphpilot
Author: graphpilot-oss

@graphpilot-oss

About Graphpilot

GraphPilot gives coding agents persistent structural knowledge of a codebase. It parses TypeScript/JavaScript with tree-sitter into a graph of symbols and call edges, then exposes that graph over MCP so the agent can recall definitions, find callers, and trace change impact witho

#mcp #model-context-protocol #code-intelligence #structural-memory #typescript #javascript #tree-sitter #static-analysis #call-graph #code-navigation #refactoring #impact-analysis #developer-tools #coding-agents #local-first

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "graphpilot": {
      "command": "npx",
      "args": [
        "-y",
        "@graphpilot-oss/graphpilot",
        "mcp"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Graphpilot?

Graphpilot is a local CLI + MCP server that indexes TypeScript/JavaScript repos into a structural graph (symbols, callers, callees, blast radius) and exposes it to coding agents like Claude Code, Cursor, and Cline, so they stop grepping the same files every session. It runs entirely on your machine and serves as persistent structural memory between agent sessions, reducing token usage and hallucinations.

How to use Graphpilot?

Install the package globally (npm install -g @graphpilot-oss/graphpilot), then run graphpilot index <path> once to build the graph. For agent integration, add a two-line MCP server entry to your agent's configuration pointing to graphpilot mcp. Optionally run graphpilot watch <path> for sub-second incremental updates and graphpilot init to write editor rules that teach the agent to use the gp_* tools.

Key features of Graphpilot

Evidence anchors with file:line@sha on every result
Differential impact scoped to branch changes via since
Worktree‑aware indexing without manual configuration
Local‑first, zero telemetry, deterministic graph
Sub‑second incremental watch mode updates
Four MCP tools: gp_recall, gp_callers, gp_impact, gp_index

Use cases of Graphpilot

Find all callers of a function before refactoring
Assess blast radius of renaming a symbol up to depth 5
Perform PR‑scoped impact analysis using branch filter
Locate a symbol definition quickly without grep
Keep agent’s structural knowledge fresh via watch mode

FAQ from Graphpilot

What are the prerequisites for using Graphpilot?

Node.js ≥20, an MCP‑capable coding agent (Claude Code, Cursor, Cline, Windsurf, or Continue), and a TypeScript or JavaScript repository to index.

How does Graphpilot compare to grep?

In a benchmark on 10 structural queries, Graphpilot achieved F1 0.89 vs grep’s 0.42 while reading 99.9% fewer bytes (721 B vs 528 KB). An agent using Graphpilot on 40 questions used 61% fewer tokens and cost $3.68 instead of $8.88.

Does Graphpilot send any data off my machine?

No. Graphpilot is local‑first by design — it has no telemetry, no remote calls, and the

Comments

More Other MCP servers

🚀 Model Context Protocol (MCP) Curriculum for Beginners

microsoft

This open-source curriculum introduces the fundamentals of Model Context Protocol (MCP) through real-world, cross-language examples in .NET, Java, TypeScript, JavaScript, Rust and Python. Designed for developers, it focuses on practical techniques for building modular, scalable,

16.7K