An r/ClaudeAI launch documented Semble cutting Claude Code grep+read token cost dramatically on large repos. This walks pairing local code search MCP with Scavio for out-of-repo grounding (framework docs, recent issues, Stack Overflow).
Prerequisites
- Claude Code CLI
- A large repo (>100K LOC) where grep+read is expensive
- Scavio API key
- (Optional) Semble or another local code search MCP
Walkthrough
Step 1: Install Semble (or equivalent) for in-repo code search
Local index, no cloud upload.
# Per Semble docs (verify current install command at the project's README):
# git clone <semble-repo> && cd semble && <install steps>Step 2: Add Semble as MCP to Claude Code
One CLI line.
claude mcp add semble <semble-mcp-url-or-path>Step 3: Add Scavio as MCP for out-of-repo grounding
Web search, framework docs, etc.
claude mcp add scavio https://mcp.scavio.dev/mcp --header 'x-api-key: $SCAVIO_API_KEY'Step 4: Tell Claude in the system prompt which tool to pick when
Explicit routing rules.
// 'For in-repo code questions, call semble.search. For framework docs, recent issues, or Stack Overflow questions, call scavio.search. Do not use grep+read for in-repo lookups.'Step 5: Try a typical task and watch the trace
Should NOT see grep+read fanout.
// 'Find where we handle pagination in the API and update the cursor logic to support backward pagination.'
// Trace should show: semble.search('pagination') → 3-5 ranges → edit those.Step 6: Compare token cost vs the old grep+read pattern
Honest measurement.
// Run the same task with Semble disabled, then enabled. Expect 80-98% token reduction on large repos.Python Example
# No code; this is a Claude Code config tutorial. Input tokens drop from tens of thousands to hundreds per query on large repos.JavaScript Example
// Same — MCP config, not application code.Expected Output
Claude Code with two clearly-named MCPs: Semble (in-repo) and Scavio (out-of-repo). Token cost on large repos drops dramatically; routing is explicit; no overlap.