Repo Cartographer runs on your own machine — the client starts it, so there is no endpoint to ping. 65 installs a week from npm. Last commit 5 Aug 2026.
Maps any repo into an architecture diagram (Mermaid/Graphviz) and enforces architecture rules in CI
Nothing serious here today
Today is the operative word: we check Repo Cartographer every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add repo-cartographer -- npx -y repo-cartographer{
"mcpServers": {
"repo-cartographer": {
"command": "npx",
"args": [
"-y",
"repo-cartographer"
]
}
}
}[mcp_servers.repo-cartographer]
command = "npx"
args = ["-y", "repo-cartographer"]{
"mcpServers": {
"repo-cartographer": {
"command": "npx",
"args": [
"-y",
"repo-cartographer"
]
}
}
}{
"servers": {
"repo-cartographer": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"repo-cartographer"
]
}
}
}Alternatives to Repo Cartographer
same job, measured the same wayArchitecture diagrams, explanations and Mermaid source for public GitHub repositories.
Render and validate diagrams as code: Mermaid, PlantUML, C4, Graphviz, D2 and more.
Deterministic repo architecture maps: auth coverage, blast radius, readiness score, diagrams
Mine the architecture rules your TypeScript repo already enforces, with the evidence attached.
Author, validate, lay out, render, and diff architecture diagrams as code.
Always-fresh local repo graph: LSP-backed impact, Health, dead code, endpoints, architecture.
Mermaid to assets. Source code to maps. MCP for agents.
Design transformer LLM architectures and report their parameters, FLOPs, memory and cost
Repo Cartographer — questions
Answers built from our own checks of this server.