repo-cartographer
Related Servers
Alternatives to repo-cartographer
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceMCP server for repository mapping, dependency analysis, and architecture diagram generation for JavaScript, TypeScript, and Python projects.48 npm-
- FlicenseNot gradedqualityDmaintenanceMCP server for automated architectural mapping, security vulnerability detection, ML asset tracking, and code metrics in local repositories.-
- FlicenseAqualityCmaintenanceMCP server for generating and editing architecture diagrams from natural language or code, supporting formats like Terraform, docker-compose, Kubernetes, SQL, Mermaid, and PlantUML.2-
- AlicenseNot gradedqualityAmaintenanceLocal-first MCP server that scans a repository once and answers architecture questions from an evidence-backed graph, enabling dependency analysis, impact analysis, and codebase exploration without re-reading the source tree.3MIT
- FlicenseAqualityBmaintenanceAn MCP server that generates standalone SVG architecture diagrams from text descriptions, running entirely on your machine with no dependencies or network access.8-
- AlicenseNot gradedqualityCmaintenanceMCP server for rendering Mermaid diagrams and generating source-code diagrams, with tools to render text/files and produce dependency/class diagrams.50 npmMIT
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.