The original title is "MCP went stateless. Your agent workflow did not."

Short summary

MCP's 2026-07-28 stable revision introduces a stateless, sessionless core that fits ordinary HTTP infrastructure better, removing the initialization handshake and protocol-level sessions. State across calls is now handled via explicit application-level handles (basket_id, job_id) rather than invisible transport state. Two new extensions—MCP Apps for interactive UIs and MCP Tasks for async operations—extend the protocol beyond synchronous tool calls, though host applications still own operational state and consent.

• •MCP 2026-07-28 goes stateless: each request is self-contained, no session affinity needed
• •Stateful workflows use explicit handles (job_id, basket_id) as application data, not transport state
• •MCP Apps and MCP Tasks extensions add interactive UIs and async operations to the protocol

Generated with AI, which can make mistakes.