Skip to content
Agentmart
Submit a tool

Repo Graph

Structural graph map of any codebase so LLMs navigate by structure, not guesswork.

Connector by James-Chahwan · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)★ 87
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/james-chahwan-repo-graph

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Structural graph map of any codebase so LLMs navigate by structure, not guesswork.

Use cases: refactoring, debugging

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools
4 read · 2 write · 0 delete
Secrets
None asked for
Install scripts
None found
Runs as
Python package

Tools by what they do 6

Read from the source code; the running server may list different tools.

Read 4 · Look things up without changing anything.

  • find
  • impact
  • orient
  • read

Write 2 · Create, change, send or run things.

  • refresh
  • trace

Secrets and settings it asks for

Other settings (environment variables or headers).

  • REPO_GRAPH_REPO

Network hosts it talks to 5

  • fonts.googleapis.com · found in code
  • fonts.gstatic.com · found in code
  • github.com · found in code
  • glama.ai · found in code
  • repo-graph.com · found in code

Files it touches

  • /home/ivy/Code/lapse
  • /home/ivy/Code/oci
  • /home/ivy/Code/quokka
  • /home/ivy/Code/quokka-stack
  • /tmp/cases.json
  • /tmp/demo-backup
  • /tmp/exrepos
  • /tmp/ogfonts
  • /tmp/repo-graph-sweep
  • Your home directory (~)
  • ~/.codex/config.toml

Tools (6)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • findFind Nodes

    Turn any text into the ranked nodes that matter — the on-ramp to the graph. A symbol or keyword returns matching nodes; a pasted stacktrace / failing-test id / diff is resolved to the code it implicates and ranked by relevance. Set `expand=true` to fan out to the surrounding neighbourhood (spreading activation). Every row carries `path:line`, so `read` the top hits directly — no grep.

  • impactImpact / Blast Radius

    Blast radius in one call: fan out from one or more nodes to everything they affect (forward) or depend on / are used by (backward), returned as a complete, deduped, Personalized-PageRank-ranked, located closure. Each row carries `path:line`, the edge `via` reason it's in scope, and a `⊘` when the engine finds it unreachable from any entry point (likely dead). Structural import/containment fan-out is excluded — no noise. Depth-1 in both directions is a node's immediate neighbours. Pass several comma-separated nodes to assess a whole diff at once.

  • orientOrient

    Get the lay of the land — ALWAYS the first call on a codebase. With no arguments: a counts + entry-points overview plus a `blind spots` note flagging which (language, edge-kind) extractions are partial so you know where to fall back to grep. With `seed=<node>`: the dense structural map scoped to that node's neighbourhood. With `full=true`: the whole-repo dense map (the full context dump). Orient first, then `find` to jump to nodes, `impact` for blast radius, `trace` for flows.

  • readRead Source

    Return the source code for one or more nodes, sliced from their files by the graph's line spans. Use after `find`/`impact` to read the exact code without grepping — comma-separate several node names to read the whole ranked set in a single call. Each node is a code block headed by its qname and `path:start-end`, plus a `context:` footer with structural facts the source alone doesn't show: HTTP method, cross-stack callers (or, on a WS / gRPC / GraphQL / tRPC client, the host it dials), covering tests, and intent/decision/constraint cells when present.

  • refreshRefresh Graph

    (Re)build the structural graph with tree-sitter AST parsing across 20 languages, running the cross-stack resolvers (HTTP, gRPC, GraphQL, WebSocket, queues, events, CLI). Incremental by default — only changed files re-parse — so it's cheap to call after edits; set `full=true` to force a clean reparse. Accepts a local path or a git URL (cloned on demand). Call after a major refactor; routine edits are picked up automatically by the file watcher.

  • traceTrace

    Follow the code across boundaries. One argument: trace a feature end-to-end — the ordered path from entry through the stack, each hop labelled with its mechanism (call / HTTP / queue / event / data), crossing service boundaries (frontend→backend). Two arguments: the shortest path between two specific nodes, hop by hop. This is where the graph beats reading many files — it knows the cross-stack links grep can't see.

Signals

Stars
87
Forks
1
Open issues
1
Contributors
1
Weekly downloads
209
Last commit
Oct 2, 2026 (27 days ago)
Last release
Oct 2, 2026 (27 days ago)
Last package publish
Oct 2, 2026 (27 days ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.James-Chahwan/repo-graph
Version
0.5.2
Auth
No auth
Packages
pypi mcp-repo-graph
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from James-Chahwan

Cite this page

Repo Graph MCP server. Agent Mart. https://agentmart.dev/connectors/james-chahwan-repo-graph (last updated 2026-10-24)