Architecture docs from a repo: overview, modules, API surface, routes, dependency graph, diffs.
Connect Runs on your machine
claude mcp add repolens -e REPOLENS_WORKSPACE=<REPOLENS_WORKSPACE> -- npx -y @chappibunny/[email protected]{
"mcpServers": {
"repolens": {
"command": "npx",
"args": [
"-y",
"@chappibunny/[email protected]"
],
"env": {
"REPOLENS_WORKSPACE": "<REPOLENS_WORKSPACE>"
}
}
}
}{
"mcpServers": {
"repolens": {
"command": "npx",
"args": [
"-y",
"@chappibunny/[email protected]"
],
"env": {
"REPOLENS_WORKSPACE": "<REPOLENS_WORKSPACE>"
}
}
}
}{
"servers": {
"repolens": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@chappibunny/[email protected]"
],
"env": {
"REPOLENS_WORKSPACE": "<REPOLENS_WORKSPACE>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
REPOLENS_WORKSPACEOptional | Absolute path of the repository to read. Defaults to the process working directory. Every tool path must stay inside this directory. |
Details
| Package | @chappibunny/[email protected] (NPM, stdio) |
| First published | 13 Nov 2026 |
| Last updated | 13 Nov 2026 |
| Registry name | io.github.CHAPIBUNNY/repolens |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.