Summer Engine Shrinks MCP Context 70%

The strongest idea here is operational consistency, not the headline token savings: a single catalog gives agents safer, more portable access to a rapidly expanding toolset.

• –Hosted clients that load every tool saw 70% fewer first-call input tokens, but Codex saw no reduction and Claude Code gained only 21%.
• –Search-and-call scales better than exposing hundreds of specialized tools, provided natural-language retrieval remains reliable.
• –Dry runs, typed schemas, structured errors, approval gates, and idempotency keys make agent-triggered mutations safer to retry.
• –The 168-session evaluation matched tuned 3.x performance, but used fixtures rather than real accounts or live engine runs.
• –Mirroring the same operations across MCP and CLI reduces implementation drift and lets developers switch interfaces without relearning the platform. [GitHub](https://github.com/SummerEngine/summer)