Who it is forA DevOps engineer building an AI review step in CI that should not paste the whole repo into a prompt.
The problemDumping a full repo into an LLM blows the token budget and buries the relevant code.
The outcomemap.json and pack.json your pipeline can pass to a model, focused on the folders that matter.
What you need first
- Node.js 18+
Steps
- Run
git clone https://github.com/nduc99911/repo-context-mcp.git,cd repo-context-mcp,npm installandnpm run build - Run
node dist/cli.js map . --jsonfrom your project root and save the output as map.json - Run
node dist/cli.js pack . --focus src --jsonfor a focused pack and save it as pack.json - Cap size with
node dist/cli.js pack . --focus auth,api --max-tokens 8000 - Feed the JSON to your review script in CI
Prompt for your agent
In CI, run repo-context-mcp's `map . --json` and `pack . --focus <dirs> --max-tokens <n>`, then review only the packed files for <goal>. Report the token count and list any changed file the pack left out.
Caveat. The npx package is marked as after publish in the README, so build from source in CI until it is on npm.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for nduc99911/repo-context-mcp and "Generate repo maps as JSON for CI and scripts"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer