Repo Map

Call the get_repo_map tool (from the repo-map MCP server) when you need a structural overview of a codebase without reading every file:

• Orienting in an unfamiliar repository or subdirectory.
• Before making a change that likely touches multiple files, to find related classes/functions cheaply.
• When you already know which files you're about to edit, pass them as focus_files (repo-relative paths) so the map surfaces those files and whatever else references or is referenced by them, ranked to the top.

Arguments:

• project_root (optional): a repo-relative subdirectory to scope the map to, e.g. "src/backend". Defaults to the whole repo. Do not pass an absolute host path — the tool only sees the repository at its container mount point.
• focus_files (optional): list of repo-relative paths to prioritize.
• max_tokens (optional): approximate size budget for the returned map.

Prefer this over opening files one by one to guess at project structure. It does not replace reading a file's actual body once you've identified it as relevant — the map gives signatures and line numbers, not implementations.