The Problem
Default grep+read on a 100K+ LOC repo fans out across 8-15 files per query, costing tens of thousands of input tokens. Multiplied across a Claude Code session, the bill grows fast.
The Scavio Solution
Local code search MCP (Semble or equivalent) for in-repo lookups + Scavio MCP for out-of-repo grounding (framework docs, Stack Overflow, recent issues). Two named MCPs, no overlap.
Before
An r/ClaudeAI post documented the token blowup; default grep+read fanout = 30-50K input tokens per find-and-edit query.
After
Indexed code search returns matching ranges (a few hundred tokens) + Scavio handles out-of-repo. Token cost on large repos drops 80-98% per query.
Who It Is For
Claude Code users on large repos (>100K LOC), engineering teams paying for Anthropic-routed agents, devs with token-cost anxiety.
Key Benefits
- Token cost drops 80-98% on large repos
- Local-only code search (no cloud upload)
- Scavio handles out-of-repo grounding under one MCP
- Two clearly-named MCPs, clean tool surface
- Per-week LLM bill drops 30-50% for heavy users
Python Example
# Setup is via Claude Code CLI:
# claude mcp add semble <semble-url> # local code search
# claude mcp add scavio https://mcp.scavio.dev/mcp --header 'x-api-key: $SCAVIO_API_KEY'
# Plus a system prompt rule: 'Use semble for in-repo, scavio for out-of-repo. Don't grep+read.'JavaScript Example
// MCP setup — no JS application code.Platforms Used
Web search with knowledge graph, PAA, and AI overviews