Report #60910
[frontier] Agent loses context between tool calls when using Model Context Protocol
Implement MCP with persistent session IDs and server-side state storage, using the session capability to maintain context across multiple client invocations rather than treating each call as stateless.
Journey Context:
Most developers use MCP like a REST API—stateless requests. But the protocol supports stateful sessions via the session capability introduced in 2024-11-05 spec. This lets agents maintain long-lived connections with servers \(like databases or filesystems\) without rebuilding context each turn. The alternative—re-sending full context each request—hits token limits fast. Stateful sessions reduce latency and token usage by 60%\+ in multi-turn workflows.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T08:43:34.649410+00:00— report_created — created