In July 2026, MCP transitioned its core protocol design from session-based to stateless, eliminating the need for sticky sessions, session stores, and complex handshake steps. This shift directly impacts AWS MCP server deployment by simplifying infrastructure, improving scaling, and aligning with the AWS Well-Architected Agentic AI Lens.
- Eliminates sticky sessions and shared session state
- Facilitates easier horizontal scaling and cost reduction
- Simplifies developer workflow with stateless request handling
Infrastructure signal
The stateless MCP core removes critical infrastructure components previously needed to support session-based protocols on AWS. These components included load balancer sticky sessions and session stores such as DynamoDB or ElastiCache, which were required to keep session context consistent across server instances. Removing these dependencies simplifies the deployment topology, decreasing operational overhead and cloud resource costs.
Additionally, servers no longer maintain ongoing session state locally or externally during request processing. Instead, all necessary context is included in each individual request, enabling any server instance to respond. This design aligns with modern AWS Well-Architected Framework best practices, particularly improving scalability and reliability by eliminating session affinity and enabling seamless horizontal scaling.
Developer impact
Developers benefit from the stateless MCP protocol as it removes the need for managing session initialization handshakes and maintaining stateful session stores. This reduces complexity in application logic and testing. Tool calls, including initial client requests, now carry full context, meaning workflows can execute independently on any server without session stickiness concerns.
The protocol replaces server-initiated push patterns with Multi Round-Trip Requests (MRTR), a clearer and stateless interaction pattern. This change requires adaptation in client-server communication design but results in more predictable and debuggable workflows. Developers also gain access to a new discovery endpoint that reveals server capabilities and supported protocol versions, enabling dynamic client compatibility checks and smoother migrations.
What teams should watch
Teams running MCP behind Amazon Bedrock AgentCore Gateway or other managed proxies will see backward compatibility and protocol management largely handled automatically, but teams controlling full deployment stacks must plan migration carefully. Legacy session infrastructure can be decommissioned only after verifying no clients remain on pre-2026-07-28 protocol versions. Instrumenting gateways to capture protocol version per request is critical for monitoring transition progress.
Because the stateless protocol no longer supports server-pushed requests mid-call, applications relying on such interactions must migrate to use the MRTR pattern. This may involve redesigning API interaction models and observability practices to reflect state continuation through tokens rather than persistent sessions. Teams should also watch for changes in their operational metrics as request routing changes and session stores are retired.