CLI gives models more control over context than badly designed MCP tools
jobergum · x · 2026-07-25
The author argues that the key difference between a CLI workflow and MCP is control over context management.
- A CLI lets the model use its own context-management skills, such as bash and code mode.
- Poorly designed MCP functions can flood the model with irrelevant context.
- In that case, the model loses the ability to decide what matters and is forced to process noise it cannot control.
More from coding & agent
- Data engineering, not agent frameworks, is the real bottleneck for enterprise AI agents — dhruv2038 · 2026-09-11
- GPT-6 Astra beats Factorio with enemies in 44 in-game hours at ~$4,500 API cost — liminal_bardo · 2026-09-11
- 105 hidden bugs, 2 repos: DeepSeek V4.1 Flash fixes 24 at $1.80 vs Opus 5's 27 at $51.33 — ChartsJournalX · 2026-09-11
- Investment Analyst Asks How to Build a Claude-Based Diligence Agent Stack — Careless_Tie2286 · 2026-09-11
- Treating agents like 50 First Dates: a 3-layer context system so every conversation doesn't start from zero — evielync · 2026-09-11
- Running the Firefox MCP on Android via Termux, ngrok, and mcp-proxy — Nervous-Strain7544 · 2026-09-11