Tokengraph parses your repository into a structural graph with Tree-sitter — so Claude Code, Cursor, and other assistants read only the functions, callers, and tests that actually matter to a change.
To touch one function, an assistant without a map re-reads whatever it can find. Tokengraph already knows what connects to what, so it hands over a slice instead of a dump. Pick a task to see the difference.
Illustration on a ~40k-line repository, not a benchmark. Your numbers depend on repo size, language mix, and how tangled the call graph is.
build and your next prompt.Four stages run once up front, then stay current as you edit. Step through them.
This is a miniature of what Tokengraph visualize opens on a real repo. Selecting a node traces every caller, dependent, and test that a change to it would touch — that set, and nothing else, is what your assistant gets. Drag nodes to untangle them.
Tokengraph detects the assistants you already use and registers itself as an MCP server. Nothing leaves your machine — the graph is a SQLite file in .Tokengraph/.
“Build the code review graph for this project” — your assistant calls the MCP tools itself.
Hooks re-parse on file save and git commit, so the graph never drifts from the code.
No API key, no cloud, no external database. Delete .Tokengraph/ to undo it.
Free and MIT licensed. Works on any repo Tree-sitter can parse.