Madar MCP server

Madar

Give your coding agent the repo context it needs before it starts searching.

Madar builds a local graph of your TypeScript or Node.js repository and turns the current question into a small, task-aware context pack. Claude Code, Codex, Cursor, Copilot, Gemini, Aider, and OpenCode can start from relevant files, symbols, snippets, and relationships instead of rediscovering the repository from scratch.

• Start smaller: give the agent likely entrypoints and runtime paths before broad search.
• Stay local: graph generation does not upload your source code or require a cloud service.
• Stay current: installed MCP profiles refresh the graph as the active workspace changes.

Try It in 60 Seconds

Install Madar with Node.js 20 or newer, then run it inside your repository:

npm install -g @lubab/madar
cd your-repository
madar try "how does authentication work?"

madar try builds or reuses the local graph, prints a human-readable first result, and recommends the next agent-install command. It does not modify your source code.

For a concrete example, Madar's included password-reset workspace contains this path:

account-routes.ts
  -> PasswordResetService.requestPasswordReset()
  -> userRepository.saveResetToken()
  -> enqueueResetEmailJob()
  -> sendPasswordResetEmail()

That is the kind of focused starting path Madar gives an agent before it decides whether any additional file inspection is necessary.

Connect Your Agent

Choose the agent you use. For Claude Code:

madar claude install
madar doctor
madar status

After installing a profile, run madar doctor and madar status. The agent can then ask Madar for context when you use normal prompts such as:

How does authentication work?
Why does this endpoint return 403?
Where is the report generated?
What breaks if I change this service?
Add telemetry to this flow.

Madar supports these project-local installers:

Installer details are in the CLI and MCP reference. Step-by-step setup and smoke tests are in the agent quickstarts.

After upgrading Madar, rerun your agent's install command to refresh its managed profile. Older profiles may lack automatic refresh or Codex's longer startup window.

Codex installs create a workspace-scoped MCP block with longer startup and tool timeouts. Madar stays available during initial reconciliation; graph-backed calls become available once the graph is ready.

Starting with 0.31.3, a graph-backed call made while Madar is starting, pending, or reconciling returns a structured retryable response. The agent should retry the same Madar request after the suggested delay instead of bypassing Madar or running generation manually. A dead refresh owner is recovered automatically; only failed, incomplete, or policy-mismatched graph states ask for repair.

What Changes for the Agent

Without Madar, a coding agent often begins with broad filename searches, repeated reads, and guesses about which route, service, or handler owns the task.

With Madar, the first pass can include:

Shortened. The full README is on GitHub.