Filesystem Beats MCP in Production Agent Benchmark: 27% Cheaper, 32% Faster
ml_guy1 · reddit · 2026-08-19
The Locality team (note: the author works on the product, so results are conflicted-of-interest) ran the same agent harness, model, prompts, and machines across 20 production cross-app scenarios (Slack, Notion, Linear data), comparing official MCP integrations versus synchronizing the same data as mounted files via Locality. Each scenario ran 3 times with 180 blind randomized comparisons. The filesystem setup:
- Produced higher-quality answers in 70% of blind evaluations
- Cut LLM costs 27% and latency 32%
- Required 61% fewer tool calls and 40% fewer tokens
Traces show gains came from context gathering, not reasoning: in one scenario comparing evidence across Slack/Linear/Notion/Git, the filesystem agent finished an evidence-gathering stage in 0.3s with parallel rg and file ops, while the MCP agent made 21 calls over 1 minute. Conclusion: a filesystem gives agents one composable interface for searching, filtering, and reading across sources; MCP's per-app interfaces create longer retrieval chains for context-heavy work — though MCP may still be better for individual actions and lightweight integrations.
Related event: File System Sync Found Up to 100x Faster Than MCP for Agents(2 posts)→
More from coding & agent
- GitHub Commits Surge to 1.4B/Month as Cursor Launches Origin Code Hosting — krishnan · 2026-08-20
- Joke becomes reality: Cursor Origin mirrors 'fork caching' concept — willccbb · 2026-08-20
- Reality Check skill keeps agents on track and reduces hallucinations — doodlestein · 2026-08-20
- VSIINK: Using Unicode Variation Selectors for Invisible Ink Encoding — Singularity_Warrant0 · 2026-08-20
- Benchmark: pi agent harness outperforms DeepSeek's dsh on cost — solyarisoftware · 2026-08-20
- Anatomy of an AI Agent: Diagram explains universal architecture from perception to execution — blaizedsouza · 2026-08-20