code-review-graph — MCP Context for Smarter Reviews

Main

• Run install once per machine to generate MCP config, then restart your tool so it can discover the server.
• Use the graph as a review gate: ask for blast radius + minimal file set before edits, then iterate with smaller diffs.
• Use README timings as sanity checks: ~10s initial build for ~500 files; incremental updates under ~2s for a 2,900-file repo (per docs).

Source-backed notes

• README says it parses repos with Tree-sitter, stores a graph, and serves context through MCP for agent review loops.
• Quick Start shows pip install + install + build as the minimal loop.
• README lists per-platform flags like --platform codex / cursor / claude-code / copilot-cli.

FAQ

• Do I need MCP support in my tool?: Yes—your editor/agent must be able to load MCP servers, or you’ll only use the CLI locally.
• Will it read my entire repo every time?: The stated goal is the opposite: build once, then incrementally update and serve minimal context.
• What’s the fastest way to get started?: Use pipx, run install --platform <tool>, restart the tool, then run build.