repomap MCP server

repomap

<!-- oneliner -->A map of your codebase for AI agents: code graph, search, call paths and change impact. No API key.<!-- /oneliner -->

Code graph · hybrid search · call paths · change impact · an interactive graph UI. One Rust binary. Local. No API key. MIT.

<!-- repomap:agent-ready --><!-- /repomap:agent-ready -->

Live demo · Docs · Quickstart · Tools · Graph UI · Benchmarks · Compare

The real UI on excalidraw (687 files, indexed in under half a second): search, a symbol's code and callers, then the blast radius of a change. Try it in your browser, no install needed.

Quickstart

npx -y @sylphx/repomap setup     # add repomap to Claude Code, Codex, Cursor, VS Code, Claude Desktop, Windsurf, Gemini CLI
npx -y @sylphx/repomap serve     # open the graph UI for the current repo

That's it. Add --claude-hooks to also enrich Claude Code's Grep and Glob. setup detects the clients you have, writes their MCP config, and prints every change it made. Run it again and nothing changes. Then ask your agent: "Use repomap to map this repo."

Manual MCP config

{
  "mcpServers": {
    "repomap": { "command": "npx", "args": ["-y", "@sylphx/repomap", "mcp"] }
  }
}

Claude Code: claude mcp add repomap -- npx -y @sylphx/repomap mcp Codex (~/.codex/config.toml):

[mcp_servers.repomap]
command = "npx"
args = ["-y", "@sylphx/repomap", "mcp"]

Docker (stdio, amd64/arm64):

{ "mcpServers": { "repomap": { "command": "docker", "args": ["run", "-i", "--rm", "-v", "/path/to/repo:/workspace:ro", "ghcr.io/sylphxai/repomap"] } } }

The server indexes the client's workspace root (or its working directory, or REPOMAP_ROOT). Every tool also takes root.

Why

Agents burn most of their context on grep, ls and reading whole files just to work out where things are. repomap gives them the map up front:

• Where is it? Hybrid search that matches symbol names and the words inside functions, with the lines that matched.
• What is this? One call returns a symbol's code, callers with call-site lines, callees, subtypes and the tests that reach it.
• How does A reach B? The shortest call path, each hop cited file:line.
• What breaks if I change this? Direct and indirect callers, importing files, modules touched, tests to run, and a risk level. Point it at your git diff before you commit.
• What does this repo look like? Modules found from real dependencies (not just folders), the most central files, the most used symbols, and entry points.

All of it comes from a local index: tree-sitter parsing, a resolved import and call graph, PageRank, Louvain communities and BM25 over AST chunks. Nothing leaves your machine, and no model or embedding API is called.

What your agent gets

Shortened. The full README is on GitHub.