Local-First Code Intelligence
ARGYPH
One read-only MCP server for grep, symbols, semantic search, and repo packing.
19 read-only tools
tiered local index
npm, crates.io, and Homebrew
Problem
Giving an agent useful repository context often means wiring together multiple servers, processes, and cloud services. That increases setup cost and can move proprietary source outside the developer's machine.
System
Three-tier local index behind one ask-first MCP endpoint. Lead claim: stop wiring six MCP servers.
Evidence
Tier-zero indexing under a second, benchmark evidence, 19 read-only tools (`ask` through `memory_forget`) across npm/crates/Homebrew.
Outcome
Argyph ships as a read-only MCP server and CLI through npm, crates.io, Homebrew, and release binaries, with incremental indexing and nineteen tools across retrieval, symbols, packing, and local memory.
System
Ask-first local index
One read-only MCP endpoint over a three-tier index, nineteen tools, and bounded span results.
Approach
I built a tiered Rust index that becomes useful immediately: file inventory first, symbol and structural indexes next, then local embeddings in the background. Queries return bounded spans and disclose index coverage so the caller knows what evidence was available.
Constraints
Local-first read-only tools; no write-path claims without explicit user action. `locate_smart` stays opt-in and disabled by default.