KDCube
← AI Industry News

MCP Goes Stateless as AWS Retires Its First-Gen Agents

The Model Context Protocol's 2026-07-28 spec rewrote the core to be stateless, and Cloudflare's MCP v2 already runs it in production on Workers with a formal deprecation clock ticking on Roots, Sampling, Logging, and HTTP+SSE. Meanwhile AWS closed Bedrock Agents to new customers and pointed builders at...

Lead signal — Agent runtime reshuffle

The agent runtime layer is being re-poured underneath everyone.

MCP goes stateless, AWS sunsets its first-generation agent service, and managed harnesses reach GA — the plumbing for production agents is shifting all at once.

mcp agent-runtime governance connectors
  • The Model Context Protocol's 2026-07-28 specification rewrote the core to be stateless — every request now stands alone, so MCP servers can run behind a plain load balancer with no sticky sessions or shared storage (MCP Blog)
  • Cloudflare shipped MCP v2 on Workers off that spec, with early adopters already in production and a formal Active/Deprecated/Removed feature lifecycle (Cloudflare)
  • AWS moved Bedrock Agents into "Classic" maintenance mode, closing it to new customers as of July 30 and pointing all new builds at AgentCore (AWS Docs)
  • Microsoft's Agent Framework Harness and Foundry Hosted Agents reached general availability, shipping as a single binary across local, container, and hosted deployment (InfoQ)

Key Signals

  1. MCP is now stateless at the protocol layer — spec dated 2026-07-28, SDKs current as of this week

    The headline change moves MCP from a permanently-open connection to self-contained requests, adding multi-round-trip requests, header-based routing, cacheable list results, and a formal extensions framework. All four Tier 1 SDKs now speak the new spec, and third-party registries index tens of thousands of servers — so the ecosystem, not just the protocol, is what builders now have to track (MCP Blog).

  2. The deprecation clock is running on old MCP surfaces — 2026-07-28 lifecycle

    Roots, Sampling, Logging, Dynamic Client Registration, and the legacy HTTP+SSE transport are all now deprecated, with a guaranteed minimum 12-month migration window before removal. Cloudflare's MCP v2 leans directly on the stateless core to run servers "in just a Worker," cutting the stateful infrastructure operators previously had to babysit (Cloudflare).

  3. AWS retired its first-generation agent stack — closed to new customers July 30, 2026

    Amazon Bedrock Agents (launched November 2023) is now Bedrock Agents Classic: existing workloads keep running, but the model catalog is frozen and no new features arrive. AWS explicitly recommends migrating to AgentCore, its framework-agnostic runtime with separate services for runtime, gateway, memory, identity, and observability (AWS Docs).

Why It Matters / What To Watch

  1. Re-platform your MCP servers before the offramp closes.
    • Audit any server still relying on Roots, Sampling, Logging, or HTTP+SSE and plan the move to the stateless transport within the 12-month window (MCP Blog).
    • If you run agents on Cloudflare, MCP v2 lets you collapse stateful session infrastructure into Workers — test the migration path and feature-lifecycle flags now rather than after a deprecation lands (Cloudflare).
  2. Treat Bedrock Agents as legacy and cost the migration.
    • New agent projects on AWS should start on AgentCore; Classic will not get new models or features, so anything built on it is accruing migration debt from today (AWS Docs).
    • Compare AgentCore's split runtime/gateway/memory/identity model against the governed, consumption-billed Microsoft Agent Framework Harness — both are converging on "who ran it, under which policy, where the trace lands" as the unit of control (InfoQ).
  3. The connector layer is where enterprise data now enters agents.
    • Watch the MCP-server land grab: vendors like 6sense are shipping MCP servers that drop account and intent data straight into Claude, ChatGPT, and Agentforce with no custom integration — a preview of how quickly your internal tools may become agent-callable (AI Agent Store).

Quick Links