repo-cartographer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| map_repoA | Point at a folder and get a downloadable architecture diagram in one call: runs scan + import-graph + render internally and returns the HTML path, a facts summary, and the draft diagram source inline. By default writes architecture.html plus the raw source (.mermaid or .dot) into the repo; pass outPath to write elsewhere. Use the granular tools (scan_repo, build_import_graph, generate_diagram, render_diagram) only when you need to compose the steps yourself. |
| scan_repoA | Deterministically extract facts from a local repo: programming languages, frameworks/libraries, entry points, top-level modules (with role guesses), and a manifest summary. Returns JSON facts only — no interpretation. |
| build_import_graphA | Extract intra-repo import/require relationships for JavaScript/TypeScript and Python. Nodes are files (auto-collapsed to module/directory level for large repos); edges are directed import relationships. Returns JSON. |
| generate_diagramA | Combine scan + import facts into a DRAFT diagram string — Mermaid flowchart (default) or Graphviz DOT. level 'high' (default) shows modules/directories; 'detail' shows files grouped by module. This is a draft the calling model is expected to refine. |
| render_diagramA | Write a self-contained, shareable HTML page (renders via CDN: Mermaid, or Viz for Graphviz DOT) plus the raw source file (.mermaid or .dot). Returns the absolute paths written. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| author | Who built repo-cartographer and how to get in touch. |
TDQS
Scored across 5 tools
Each tool has a distinct role: scan_repo extracts facts, build_import_graph extracts import relationships, generate_diagram produces a draft string, render_diagram writes HTML files, and map_repo is a clearly labeled convenience wrapper that explicitly says when to use the granular tools. No two tools have overlapping purposes.
All tool names follow a consistent verb_noun pattern in snake_case: scan, build, generate, render, and map as verbs; repo, import_graph, and diagram as nouns. The naming scheme is uniform and predictable.
Five tools perfectly cover the repository mapping workflow. The high-level convenience tool plus four granular tools avoid bloat while providing flexibility. This is well within the ideal 3-15 range.
The tool set covers the full pipeline from repository scanning to dependency graph extraction to diagram generation and rendering. The convenience tool ties everything together, and there are no missing critical operations for the stated purpose.