Repo Graph MCP server

repo-graph

Structural graph memory for AI coding assistants. Map your codebase. Navigate by structure. Read only what matters.

repo-graph gives LLMs a map of your codebase — entities, relationships, and flows — so they can navigate to the right files without reading everything first.

Instead of flooding an LLM's context window with your entire codebase (or hoping it guesses right), repo-graph builds a lightweight graph of what exists, how things connect, and where the entry points are. The LLM queries the graph, finds the minimal set of files it needs, and reads only those.

It pays off most where that's hardest to do by hand: large repos, monorepos that span several languages, and multi-service systems where a feature's path crosses files, stacks, and service boundaries. On a small single-language project a model can just read the files — see Where it fits best for the honest sweet spot.

Install in one click:

Or one command in your terminal wires up every agent you have: uvx mcp-repo-graph install (see Install).

### ⚠️ Upgrading to 0.5.0

The engine package was renamed repo-graph-py to glia-py. If you install with uvx or

pip install mcp-repo-graph, you don't have to do anything. The new engine is pulled in for you.

You only need to act if you import the engine directly:

diff

- import repographpy as rg

+ import glia_py as rg

Three other things changed in that same release:

- The answers are Python objects, not JSON strings. find, resolve, blast_radius,

crossstacktrace and governing_docs return a {"results": [...], "absence": {...}} dict.

If you were doing json.loads(...) on a result, drop it.

- findnode and findnodesbyqname are gone. One find(query, top_k) replaces both.

- The graph cache moved from .ai/repo-graph/ to .glia/graph/. It's rebuilt automatically,

so you can delete the old directory. The new one ignores itself and never shows up in

git status.

The six MCP tools are unchanged (orient, find, impact, trace, read, refresh), so

nothing in your agent config needs touching. Full detail in the

0.5.0 release notes.

Demo

https://github.com/user-attachments/assets/a1e4171b-b225-40d4-9210-39453e14b76a

https://github.com/user-attachments/assets/fc3191e5-fc35-4bd7-8372-72af55995883

Same bug, same model, same prompt — the only difference is whether repo-graph is installed.

The task: fix a reversed comparison operator in a Go + Angular monorepo.

(Recorded on an earlier engine, which mapped that repo to 566 nodes / 620 edges. The 0.5.0 engine extracts far more from the same code, 2,939 nodes and 5,129 edges, so the graph the model gets today is richer than the one in the video. The token and time figures are from the recorded run and are left as measured.)

Shortened. The full README is on GitHub.