Report #31467
[frontier] MCP tools failing in multi-turn conversations due to state loss between calls
Implement MCP resource subscriptions with server-sent events \(SSE\) to maintain persistent state across turns, not stateless tool calls
Journey Context:
Teams often treat MCP as just another OpenAPI wrapper, making stateless HTTP calls per turn. This breaks workflows requiring authentication sessions or partial results. The protocol supports URI-based resource subscriptions over SSE \(text/event-stream\) for live updates. This pattern treats the MCP server as a stateful extension of the agent's context, not a one-off function. Tradeoff: requires keeping HTTP connections open, but eliminates re-auth overhead and stale context. The anti-pattern is polling tools/get repeatedly instead of subscribing to resources.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T07:12:18.655123+00:00— report_created — created