Rust CLI plus MCP server
1,244 GitHub stars turned into agent-ready memory. One binary. Offline first.
cargo install jev-starsjst sync plus jst statusjst search "rust" --limit 5jst similar "rust mcp"jst curate --limit 50 twicejst search <q>FTS plus lang, topic, alive flags. Offline, 47ms.jst similar <q>Hybrid FTS plus vector RRF. Offline after embed.jst statusDead, alive, and license rollup. Offline.jst context <q>Bounded agent JSON: health plus Jev plus evidence. Start here.jst note <repo> [why]Why you starred it. Surfaces in context.jst curateJev batch, hash cached. Optional, needs key.jst syncPull stars via gh api, upsert SQLite. Needs net.jst exportSTARS.md awesome list, archived skipped. Offline.jst mcpstdio server: search, similar, context, note, status, sync, export.{
"mcpServers": {
"jev-stars": { "command": "jev-stars", "args": ["mcp"] }
}
}
7 tools: search, similar, context, note, status, sync, export. Start with context.
cargo install jev-stars jst sync jst search "rust mcp"
curl -LO https://github.com/AkashPriyadarshii/jev-stars/releases/latest/download/jev-stars-windows.exe jst sync
git clone https://github.com/AkashPriyadarshii/jev-stars.git cd jev-stars cargo build --release ./target/release/jev-stars sync
Does jev-stars need an API key? No. Search, rank, context, status, and export work offline with zero keys. Only curate needs TYPESAFE_API_KEY, once, and results cache by content hash.
How is this different from the GitHub stars page? GitHub gives a paginated list. jev-stars gives your agent a bounded context object: health, license, Jev score, and evidence excerpt in about 2k tokens.
No vectors in v0.1? FTS5 answers 1,244 rows in 47ms. BGE vectors landed in v0.2 with RRF hybrid, 330ms p50.
Limits? No TUI, no dashboard, no release tracker. No star or unstar. Read only memory over your stars.