Fetching from the wire…
Public story · 2026-07-20 · high
The tool claims 83 percent answer quality and 10x fewer tokens than exploring files one by one, per its own 31-repo benchmark.
Why now: The 32.8K-star count and 31-repo benchmark reflect the project's state as of July 20.
DeusData's codebase-memory-mcp mirrors four language servers, tsserver, pyright, gopls and rust-analyzer, in one C binary with 32.8K GitHub stars already behind it.
AI coding agents normally shell out to real tsserver or gopls processes to answer "who calls this." DeusData skips that: its own benchmark reports 10x fewer tokens and 2.1x fewer tool calls than file-by-file search, at 83% answer quality across 31 repos.
DeusData calls the binary a Hybrid LSP. It reuses those four servers' type-resolution logic to refine CALLS and USAGE edges in the codebase's knowledge graph. The summary also credits typescript-go, Roslyn and Eclipse JDT among the servers it mirrors.
Vendored tree-sitter grammars cover 158 languages for everything the Hybrid LSP doesn't touch. The whole thing indexes the Linux kernel in 3 minutes, per the project's benchmarks.
Those numbers are self-reported across 31 repos. The repo doesn't say what the other 17% of answers get wrong, or how quality was scored.
Roslyn and rust-analyzer exist because getting type resolution right takes years of dedicated work per language. Reimplementing four of them by hand in C bets that agents don't need exact resolution, only fast, cheap answers at a 10x token discount.
If 83% holds up outside DeusData's benchmark set, that's a case for baking approximation into coding tools instead of shelling out to real LSP processes. If it doesn't, the wrong 17% is the cost of skipping years of language-server engineering.
Each link below shares sources, entities, or timing with this story.
Claude Code uses LSP / Shared entity: Linux / Earlier coverage
Linked by a graph relationship (Claude Code uses LSP); both cover Linux; earlier Linux coverage from 2026-03-28.
Claude Code uses LSP / Shared entity: Linux / Same source domain / Earlier coverage
Linked by a graph relationship (Claude Code uses LSP); both cover Linux; reported by the same outlet (github.com).
Claude Code uses LSP / Shared entity: LSP / Same source domain / Earlier coverage
Linked by a graph relationship (Claude Code uses LSP); both cover LSP; reported by the same outlet (github.com).
Claude Code uses LSP / Shared entity: Usage / Same source domain / Earlier coverage
Linked by a graph relationship (Claude Code uses LSP); both cover Usage; reported by the same outlet (github.com).
Claude Code uses LSP / Shared entity: LSP / Same source domain / Earlier coverage
Linked by a graph relationship (Claude Code uses LSP); both cover LSP; reported by the same outlet (github.com).
Claude Code uses LSP / Shared entity: LSP / Shared topic / Earlier coverage
Linked by a graph relationship (Claude Code uses LSP); both cover LSP; overlapping topics (answer, call).
Claude Code uses LSP / Shared entity: Usage / Earlier coverage / Tension
Linked by a graph relationship (Claude Code uses LSP); both cover Usage; earlier Usage coverage from 2026-04-02.
Claude Code uses LSP / Shared entity: LSP / Earlier coverage / Tension
Linked by a graph relationship (Claude Code uses LSP); both cover LSP; earlier LSP coverage from 2026-04-01.