High-level map of a codebase: languages, frameworks, size, structure, and entry points. Start here to understand an unfamiliar repo.

Args: path: Repo path to analyze. Relative to the server's working directory (or MCP_ARCHITECT_ROOT if set). Defaults to the whole project.

Map how internal modules import each other, the most-depended-upon modules, and any circular dependencies. Use to understand coupling.

Args: path: Repo path to analyze. language: 'auto', 'python', or 'js'/'ts'.

What could break if you change target? Walks the import graph backwards to list direct importers and the full transitive blast radius, and flags whether the target is a high-risk hub. Use before editing/refactoring a module.

Args: target: Module or file to analyze, e.g. "app/core/db.py" or "app.core.db". If omitted, returns the highest-impact modules to pick from. path: Repo root. language: 'auto', 'python', or 'js'/'ts'.

Find the files most worth attention: largest, most complex, most frequently changed (git), and highest combined risk.

Args: path: Repo path to analyze. top: How many files per category (default 10).

Deep-dive a single folder or file: its files, public classes/functions, and external dependencies.

Args: path: Repo root. module: Sub-path within the repo (folder or file) to explain.