Install
$ agentstack add mcp-rogerchappel-repoatlas ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ● Environment & secrets Used
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
repoatlas 🗺️
Local-first codebase intelligence for coding agents. repoatlas precomputes the boring repository facts agents keep rediscovering: file roles, import edges, symbols, likely tests, and compact context packs. It is deliberately deterministic, evidence-backed, and private by default.
npm install -g repoatlas
repoatlas index .
repoatlas impact src/routes/social.ts
repoatlas pack --topic "social publishing flow" --max-tokens 8000
repoatlas mcp --stdio
Why repoatlas exists
Agents are good at editing after they understand the terrain. They are less good at repeatedly rebuilding the map. repoatlas gives them a small, repo-owned atlas before they touch code:
- Repository manifest with roles for source, tests, docs, config, CI, routes, schema, infra, and assets.
- JS/TS/Python import graph from deterministic parsing; no LLM required.
- Symbol inventory for common functions, classes, and exports.
- Impact briefs that cite dependents, likely tests, docs, config, and evidence paths.
- Context packs that fit agent prompts without dumping the whole repo.
- Read-only MCP tools for hosts that prefer tool calls over shell commands.
Commands
repoatlas index [root]
Builds .repoatlas/index.json in the target repository.
repoatlas index .
repoatlas index . --json
repoatlas impact
Shows blast radius, likely tests, related docs/config, confidence, and evidence paths.
repoatlas impact src/routes/social.ts
repoatlas impact src/routes/social.ts --json
repoatlas file
Explains a file's role, language, imports, and detected symbols.
repoatlas file src/routes/social.ts
repoatlas pack --topic "..."
Creates a compact markdown evidence pack for agents.
repoatlas pack --topic "database queue writes" --max-tokens 4000
repoatlas ask
Searches indexed paths and symbols deterministically.
repoatlas ask registerSocialRoutes
repoatlas mcp --stdio
Starts a read-only stdio MCP server with these tools:
repoatlas_searchrepoatlas_impactrepoatlas_file_briefrepoatlas_context_pack
Privacy and safety
repoatlas is local-first:
- No network calls in indexing or query commands.
- No hidden telemetry.
- No source upload.
- Default write is limited to
.repoatlas/index.json. - Common local secret files such as
.env,.npmrc, private keys,node_modules, build output, and.gitare skipped during indexing. - MCP V1 is read-only and stdio-only.
Development
npm install
npm run check
npm test
npm run build
npm run smoke
npm run release:check
bash scripts/validate.sh
release:check runs the typecheck, tests, build, smoke fixture, and package assertions used to verify the CLI before release-facing changes. Maintainers can use the [release checklist](docs/RELEASE_CHECKLIST.md) to review a candidate without publishing or tagging it.
Status
V1 focuses on useful deterministic structure for JS/TS/Python repositories. It intentionally avoids semantic search, hosted sync, and automatic refactors until local evidence quality is strong.
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: rogerchappel
- Source: rogerchappel/repoatlas
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.