RepoLens runs on your own machine — the client starts it, so there is no endpoint to ping. 1 091 installs a week from npm. Last commit 27 Oct 2026.
Architecture docs from a repo: overview, modules, API surface, routes, dependency graph, diffs.
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const content = await readFileSafe(path.join(repoRoot, file));
const child = spawn(cmd, args, {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
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 repolens -- npx -y @chappibunny/repolens
{
"mcpServers": {
"repolens": {
"command": "npx",
"args": [
"-y",
"@chappibunny/repolens"
]
}
}
}
[mcp_servers.repolens]
command = "npx"
args = ["-y", "@chappibunny/repolens"]
{
"mcpServers": {
"repolens": {
"command": "npx",
"args": [
"-y",
"@chappibunny/repolens"
]
}
}
}
{
"servers": {
"repolens": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@chappibunny/repolens"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
REPOLENS_WORKSPACE (Absolute path of the repository to read. Defaults to the process working directory. Every tool path must stay inside this directory).
Architecture guardrails for AI-written code: dependency graph, impact, dead code, CI gate
Codebase analysis: dependency graphs, security scanning, and refactor plans for GitHub and GitLab.
Maps any repo into an architecture diagram (Mermaid/Graphviz) and enforces architecture rules in CI
Always-fresh local repo graph: LSP-backed impact, Health, dead code, endpoints, architecture.
Self-hosted code intelligence: cross-repo Q&A, dependency audits and PR review, over MCP
Hosted code graph over MCP: exact callers, dependencies, and cross-repo blast radius for AI agents.
Author, validate, lay out, render, and diff architecture diagrams as code.
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Answers built from our own checks of this server.