repo2graph

Give coding agents trustworthy, cited answers about unfamiliar codebases.

Ask a repository a question; get back the actual source that answers it, every block stamped with the file and line range it came from.

English · 简体中文 · 日本語 · Français · Español · Deutsch

📦  Package	🩺  Health	🗂️  Listed on

What is it · Who it's for · vs. grep · Quickstart · MCP setup · What it won't do · Benchmarks · Architecture · Docs · Contributing

⚡ What is repo2graph?

An agent dropped into a codebase it has never seen has two bad options. Grep for a word and it either floods its context with whole matching files, or finds nothing because the code spells the idea differently than you did. Guess from training data and it writes something confident and wrong. Either way you cannot tell which of the two just happened.

repo2graph answers questions about a repository with the repository's own source. Ask "how does a request get authenticated" and you get back the function that does it, the functions that call it and the ones it calls — each block headed [cite: path:start-end], so every claim in the answer is one click from the line it came from. If the answer is wrong, the citation shows you where it went wrong. That is the whole point.

It gets there by reading the code rather than searching it: one parse pass records who calls whom, who imports what, and which class extends which, and retrieval follows those links instead of matching more text. The result is served straight into Claude Code, Cursor or any Model Context Protocol client, or packed into a markdown context with a hard token ceiling for any other LLM.

flowchart LR
    A[your code] --> B[tree-sitter<br/>reads the code]
    B --> C[graph<br/>dots + arrows]
    C --> D[graph.html<br/>the picture]
    C --> E[chunks.jsonl<br/>pieces for an AI]
    C -->|MCP stdio| F[Claude / Cursor /<br/>any MCP client]

No project setup, no language server, no build step — point it at a folder and it works.

Interactive canvas, zoomed	Filter & inspector controls

graph.html is one self-contained file — no server, no internet, drag to pan, scroll to zoom, click a node to inspect its code and neighbours.

👥 Who it's for

uvx repo2graph build . -o .r2g
open .r2g/human/graph.html
repo2graph rag "how does routing work" -o .r2g

claude mcp add repo2graph -- \
  uvx --from "repo2graph[mcp]" repo2graph-mcp .

repo2graph build . -o .r2g --git-history 500
repo2graph explain node "sym:src/auth.py::verify" -o .r2g

- uses: Srinivasan-78/repo2graph@v2
  with: { git-history: "500", commit-branch: graph }

🔎 Why repo2graph instead of grep or vector search?

Both of those are still in the box — repo2graph seeds every query with BM25, and dense vectors are an opt-in fusion. The difference is what happens after the first match.

Use grep when you want every occurrence of a literal string — a config key, an error message, a TODO. repo2graph has no special knowledge of string literals and will not beat it. Use repo2graph when the question is about relationships: what calls this, what breaks if I change it, how does data get from A to B. Longer version: docs/why-graph.md.