Repowise: 8 MCP Tools for Claude Code Cut Token Usage by 50%

Repowise is an open-source tool that pre-computes codebase context for AI coding agents. Instead of letting Claude Code read the tree, trace imports, and browse files (burning tokens on archaeology every session), Repowise indexes your codebase once and exposes the result via eight MCP tools.

How it works

Repowise indexes your codebase into four layers:

Dependency graph via AST parsing
Git behavioral signals: hotspots, ownership, co-change pairs
Auto-generated doc wiki with semantic search
Architectural decision records (ADRs) linked to the code nodes they govern

Setup is straightforward:

pip install repowise
repowise init

Works with Claude Code, Cursor, or local setup. Incremental updates after each commit run in under 30 seconds. It also auto-generates your CLAUDE.md from live graph data on every commit — hotspot warnings, ownership map, co-change pairs, active decisions, dead code candidates. Custom notes stay untouched.

Benchmark: Add rate limiting to all API endpoints

On a real 3,000-file project:

Claude Code alone: grep + read ~30 files, ~8 minutes, misses ownership and hidden coupling entirely
With Repowise: 5 MCP calls, ~2 minutes, full picture

The five MCP calls:

get_overview
get_context on the relevant modules
get_risk on the files being touched
get_why to check for prior decisions
search_codebase for any existing implementation

Claude gets complete context before touching a single file. The co-change detection is particularly useful — it surfaces files that always change together in git but have no import link, which static analysis can't find and grep definitely can't.

Multi-repo and licensing

Multi-repo support is built in: index multiple repositories and query cross-repo hotspots, ownership, and dead code in one view. Repowise is AGPL-3.0, fully self-hostable, and nothing leaves your machine.

GitHub: https://github.com/repowise-dev/repowise
Dogfooding website: https://repowise.dev

📖 Read the full source: r/ClaudeAI