How AgentCore Gateway Supports the MCP 2026-07-28 Spec

I'm Matt Wood, and this is For Your Information. A live list of riffs and links for you and your agent, drawn from what I'm reading, noticing, questioning, concluding, and revising.

With this release MCP becomes a stateless protocol that scales on ordinary HTTP infrastructure. Every request now carries protocol version, client info, and client capabilities inside its _meta parameter, eliminating the need for a one-time initialization handshake. Clients that need to learn what a server supports can call the new server/discover method at any point.

aws.amazon.com →

Connections

Supported by

Designing APIs for Agents - Freestyle Freestyle's principle that agent APIs need clarity and predictable behavior is directly embodied in AgentCore Gateway's move to a stateless, HTTP-scalable MCP design.
#aws #agentcore #agenticai #mcp | Melanie (Peiyao) Li Melanie Li's AWS AgentCore/MCP post elaborates on and corroborates the specifics of how AgentCore Gateway implements the new stateless MCP 2026-07-28 spec.
Home | Laws of UX Foundational UX heuristics like feedback and consistency are being retrofitted onto agent-facing gateway APIs such as AgentCore's MCP support.
Cedar Policy Cedar's policy evaluation engine is well-suited to authorize which MCP tools/actions agents can invoke, directly supporting gateway-level access control described here

WebMCP: Making Every Website a Tool for AI Agents Both describe competing architectural approaches to agent tool access—browser-native WebMCP versus server-side AgentCore Gateway—for exposing services to AI agents.

Type:	link
First published:	Tuesday, 28 July 2026 at 12:00 UTC
Location:	https://aws.amazon.com/blogs/machine-learning/how-agentcore-gateway-supports-the-mcp-2026-07-28-spec/
URL:	https://mattwood.fyi/i/fa45a3ef