How AgentCore Gateway supports the MCP 2026-07-28 spec
AWS Machine Learning Sean Eichenberger ● Covered by 3 sources
The Model Context Protocol (MCP) released its 2026-07-28 specification, which makes MCP a stateless protocol that scales on standard HTTP infrastructure by removing session requirements and moving protocol metadata into request headers. The update introduces explicit freshness metadata (ttlMs and cacheScope) for caching, a governed extensions system, and multi-round-trip requests to replace long-lived connections, allowing any server instance to handle requests without prior session context. These changes enable MCP servers to work with ordinary load balancers and HTTP infrastructure while maintaining backward compatibility, with upgrades remaining opt-in and existing clients continuing to work unchanged.
Why it matters
The Model Context Protocol (MCP) published its 2026-07-28 specification, the largest revision since launch: MCP is now stateless, with a governed extensions system and hardened authorization. Learn what changed and how to enable the new version on Amazon Bedrock AgentCore Gateway with a single UpdateGateway call.
