Koragraph

Install

npm install -g koragraphmcpkoragraph ingest /path/to/repo        # point it at as many repos as you likeclaude mcp add koragraph -s user -- koragraph mcp

koragraph doctor checks the whole chain and prints the exact line for any editor.

Two ways to use it from here: your agent calls the tools over MCP, or you (or a script, or a Claude Code hook) run them straight from the shell, for example koragraph explore "how does checkout work" or koragraph blast src/pay.js. Same graph either way.

Then run KORAINIT in your editor

This is the step that lights up the memory layer, so don't skip it. In your coding agent (Claude Code, Cursor, Windsurf, whatever you use), tell it:

"Read KORAINIT.md and follow it."

It imports your existing CLAUDE.md / AGENTS.md into koragraph's memory, anchored to the code each rule is about, flags any rule that points at code that's already gone, and finishes wiring koragraph into the session. Run it once per project.

Prefer zero setup? Hand the whole thing to your agent instead. Paste this from the repo you want indexed, and it installs, indexes, wires itself in, and runs KORAINIT for you:

Install koragraph and set it up for this repo, then report back:1. npm install -g koragraphmcp2. koragraph ingest .3. koragraph doctor, then run the `claude mcp add …` line it prints (or wire `koragraph mcp` into   my editor's MCP config).4. Find KORAINIT.md in the installed package (`npm root -g`, then koragraphmcp/KORAINIT.md) and   follow it: it imports my existing CLAUDE.md / AGENTS.md into memory, verified against the code.Report: nodes/edges indexed, whether the MCP connected, and KORAINIT's summary.

One map of everything you've built

Koragraph turns every repo you point it at into one live graph: a resolved structure, with an edge only where there really is one.

• Every service, file, endpoint, and table.
• The real calls between them, resolved against the syntax tree, not guessed by name.
• The edges that cross a repo boundary, where single-repo tools go quiet.

A memory that knows when the code changed

Everything your agent learns is saved locally, anchored to the exact declaration, not a line number. Rename the code and the fact follows; delete it and the fact retires. No CLAUDE.md to maintain, and it survives every upgrade.

• Failures and their fixes. The fix surfaces before you hit the same wall twice.
• Hazards, rules, corrections. Stated once, honoured every session after.
• The "let's push this to Wednesday." Deferrals and half-finished intent, parked against the code and surfaced the moment you're back.

Measurably the most accurate, scored by the compilers

Every graph is graded by an independent compiler front-end (CPython ast, go/parser, Roslyn, syn, tsc, Ripper, php-ast, ctags, swiftc), never the tool under test. koragraph wins 34 of 39 language×plane cells, and leads precision on all 39.

Call-graph recall, the hardest plane:

Reproduces from test/benchmark: pinned corpus, pinned competitor versions, pinned oracles. Full breakdown in test/benchmark/REPORT.md.

The tools

Nine tools, reachable two ways: as MCP tools in your editor, and as CLI commands in your shell. On Claude Code a hook also calls the CLI to push the relevant slice into context on every turn, so the graph gets used whether or not the agent thinks to ask. Every tool returns file:line, never pasted source. Exactly one writes.

Every query verb takes --format compact|json|paths and --budget <tokens>, so a result can be trimmed before it ever enters an agent's context. Plus the operational CLI: ingest, serve, status, doctor, diff, trace, hooks, practice, report.

Languages

c · c++ · c# · go · java · javascript · php · python · ruby · rust · swift · typescript / tsx, fully resolved, tree-sitter throughout. Plus experimental kotlin · scala · elixir · solidity · vue · zig · objective-c · ocaml · rescript.

License

BUSL-1.1. Free to use, including at work. Converts to Apache-2.0 on the change date.