retrieveLABSCO SUMMARY
The agent gets a starting path, not a directory listing.
Most code-context tools return files; this returns a shaped answer — the call chain, the dependents, the communities — which is what an agent actually needs before it decides what to open. The freshness contract is the unusual part: it tells you when the graph no longer matches HEAD instead of quietly answering from a stale index.
What it is
Madar builds a graph of a TypeScript or Node.js repository on your machine, then answers an agent's question with a small context pack — ranked files, symbols, snippets and relationships — so it starts from the relevant code rather than discovering the repo by grepping. Claude Code, Codex, Cursor, Copilot, Gemini, Aider and OpenCode all have project-local installers.
What you get
retrieve— ranked nodes, code snippets and community context for "how does X work?"impactandpr_impact— directed dependents and affected communities for a refactor, or a diff-aware blast radius and ranked review risks for a pull requestcall_chain— shortest execution paths from one symbol to anothercommunity_overview,graph_statsandgraph_summary— architecture, graph size, and a bounded deterministic first-turn overview of domains, top modules, entrypoints and runtime paths- Profiles change the surface:
--profile strictexposes onlycontext_packandcontext_expand, the default core profile the seven common graph-navigation tools, and the full surface is 27 tools viaMADAR_TOOL_PROFILE=full - Freshness is explicit — packs report whether the graph is fresh, partially stale or stale against HEAD, and
--require-fresh-contextrefuses drift instead of warning
Requirements
Node.js 20 or newer. Install with npm install -g @lubab/madar, then madar try "how does authentication work?" inside the repo to build or reuse the graph. Wire up an agent with its installer — madar claude install, madar cursor install, madar codex install and so on — then check with madar doctor and madar status. Graph generation stays local; no source is uploaded and no cloud account is needed. Package version 0.32.1.
Setup effort
One command — npm install -g @lubab/madar
USE CASES
Understanding a flow you have never read
Ask how something works and get ranked symbols with snippets and the execution path between them.
Deciding whether a refactor is safe
Get the directed dependents of the symbol you want to change and the communities the change would touch.
Reviewing a pull request with the blast radius in front of you
Turn the diff into affected areas and ranked review risks before reading the changed lines.
Orienting in an unfamiliar repository
Take a bounded overview of domains, entrypoints and top modules as the first turn of a session.
7 tools
Listed in project docs. Your client may show a different list.
pr_impactimpactcall_chaincommunity_overviewgraph_statsgraph_summaryBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
npm on PATH
INSTALLATION
Connect your client
Server setup
npm install -g @lubab/madarMCP Clients
Claude Code
madar claude installCodex
madar codex installCursor
madar cursor installGitHub Copilot
madar copilot installGemini CLI
madar gemini installAider
madar aider installOpenCode
madar opencode install