repo-graph
the problem
Your AI reads the
whole
codebase to find
one
thing.
grep. read. grep. read…
0
tokens burned, still guessing
the idea
repo-graph
maps
it instead
entities · relationships · flows
navigate, don't grep
Ask → it jumps to the code that
matters
stacktrace · feature · diff → the exact nodes
cross-stack
Frontend → backend
, linked
grep can't connect the two halves
FRONTEND
ROUTES
SERVICE
HANDLERS
DATA
Groups
component
/groups
route
/friends
route
controller
service
GetFriends
handler
SendReq
handler
MongoDB
data
one line, any AI client
uvx mcp-repo-graph
Claude · Cursor · VS Code · Codex · Gemini · Windsurf
mcp-repo-graph
· repo-graph.com