MCP goes stateless, making servers fit for serverless and edge

The Model Context Protocol has a new spec, dated 2026-07-28, and the main change is architectural. MCP moves from a bidirectional, stateful protocol to a request and response model, which means a server becomes an ordinary HTTP workload with no session to keep alive. That removes the main obstacle to running MCP on serverless and edge platforms, where holding a long-lived connection is awkward or impossible.

Two features that used to sit outside the core now ship as versioned extensions. MCP Apps lets a server draw its own interactive interface inside a Claude conversation, so a user does not have to switch tabs to act on a result. MCP Tasks handles long-running work without changes to the base protocol. Authorization now follows OAuth 2.0 and OIDC, so a server can connect to an identity provider such as Entra or Okta directly, and an administrator can provision connectors across an organization without each person setting them up. Anthropic pairs the spec with MCP Tunnels, a research preview for reaching servers on a private network, and with dashboards for tracking connector use. It reports 400 million monthly SDK downloads, four times last year, and more than 950 connectors listed. You can read the announcement here.

Why it matters

If you build or run MCP servers, the stateless core lets you deploy them like any other API on serverless or edge, and the OAuth alignment means enterprise access can go through your existing identity provider instead of a custom workaround.