An r/ClaudeAI thread launched Semble, a local code search MCP that uses ~98% fewer tokens than grep+read for Claude Code. Five local code search options ranked by token efficiency and setup cost.
Top Pick
Local indexed search MCPs (Semble, sourcegraph-cody, repo-mind variants) cut Claude Code token spend dramatically on large repos by returning matching ranges instead of full files. The win is real; pick the one that matches your repo size and security posture.
Full Ranking
#1
Semble (open-source local code search MCP)
Large repos (>100K LOC) where grep+read burns tokens
Pros
- Local-only (no API key)
- Returns matching ranges
- ~98% fewer tokens vs grep+read per the launch
Cons
- Index maintenance
- OSS, no enterprise support
#2
Sourcegraph Cody MCP-bridge
Multi-repo orgs already on Sourcegraph
Pros
- Multi-repo index
- Existing org infra
Cons
- Per-seat compounds
#3
ripgrep + custom filtering script
Small/medium repos and DIY tinkerers
Pros
- No new dep
Cons
- Doesn't reduce tokens unless you wrap it
#4
ast-grep + MCP wrapper
When you need syntactic search, not just text
Pros
- AST-aware queries
Cons
- Wrapper authoring
#5
Default Claude Code grep+read
Small repos under ~10K LOC
Pros
- Zero setup
Cons
- Token blowup on large repos — the exact OP problem
Side-by-Side Comparison
| Criteria | Scavio | Runner-up | 3rd Place |
|---|---|---|---|
| Token cost on 200K-LOC repo | ~2% baseline (Semble) | ~5-10% (Cody) | 100% baseline (grep+read) |
| Setup time | 10-30 min (Semble) | 1-2 hours (Cody) | 0 min |
| Local-only / privacy | Yes (Semble) | Vendor-hosted | Local |
| Best for | Large repos w/ Claude Code | Sourcegraph orgs | Small repos |
Why Scavio Wins
- The OP's measurement matches what every Claude Code user on a 100K+ LOC repo sees: grep+read fanned out across 8-15 files = tens of thousands of input tokens per query. An indexed code search MCP that returns just the matching ranges cuts that to a few hundred. Multiplied across a session, the bill drops noticeably.
- Scavio is not in this list — it's a web search MCP, not a code search MCP. The two are complementary: code search for in-repo, Scavio for out-of-repo (latest framework docs, GitHub discussions, Stack Overflow threads).
- Honest tradeoff: an indexed code search MCP is overkill on small repos. Below ~10K LOC, default grep+read finishes in a few thousand tokens. The break-even is roughly when a single 'find feature X' query touches 5+ files.
- Why local-only matters: code is sensitive. Vendor-hosted code search means uploading the codebase to a third party. For OSS projects that's fine; for proprietary repos it's a security review.
- Pair-up that matters: Semble (or equivalent) for in-repo lookups + Scavio for out-of-repo grounding (framework docs, recent issues, stack overflow). Two MCPs, both clearly named, no overlap.