PulseAugur
EN
LIVE 17:56:33

Model Context Protocol updates to stateless requests with explicit state handles

The Model Context Protocol (MCP) has been updated to remove protocol-level sessions, requiring requests to be self-describing. This change, effective July 28, 2026, aims to improve scalability by allowing requests to be handled by any server instance without sticky routing. To manage state between calls, the new pattern involves explicit state handles, where tools mint and return visible handles that the model can pass around, offering benefits like multi-handle support, better debugging, and explicit scoping. A new CLI tool, stateforge, has been developed to generate TypeScript/Express servers implementing this pattern, with swappable state stores like Redis and deployment configurations for Vercel and Docker. AI

IMPACT Introduces a new pattern for managing state in AI model interactions, potentially improving scalability and developer experience.

RANK_REASON The item describes a new CLI tool and a pattern for managing state in a protocol, rather than a core AI model release or significant industry event.

Read on dev.to — MCP tag →

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →

Model Context Protocol updates to stateless requests with explicit state handles

COVERAGE [1]

  1. dev.to — MCP tag TIER_1 English(EN) · Jonathan Trippett ·

    Title: MCP dropped sessions. Here's the pattern that replaces them.

    <p>The Model Context Protocol's 2026-07-28 revision removed protocol-level<br /> sessions entirely. No <code>initialize</code> handshake, no <code>Mcp-Session-Id</code> header,<br /> no held-open bidirectional stream. Every request is now self-describing<br /> and can land on any…