MCP went stateless: Is your AWS MCP server deployment well-architected?

This article explains how the MCP 2026-07-28 specification removes session-based architecture, making the protocol stateless and enabling better alignment with AWS Well-Architected Framework best practices for agentic AI workloads.

• Protocol now stateless: any server instance can handle any request without session affinity or shared session stores
• Eliminates sticky routing, DynamoDB/ElastiCache session infrastructure, and handshake overhead
• Introduces Multi Round-Trip Requests (MRTR) pattern replacing server-initiated pushes for confirmations and sampling
• Adds W3C Trace Context for end-to-end observability and header-based routing via Mcp-Method and Mcp-Name
• Implements protocol-declared caching with ttlMs and cacheScope fields for performance optimization
• Enhances security through issuer validation, client type declaration, ownership enforcement, and JSON Schema validation
• AWS Lambda becomes first-class pattern; serverless deployments no longer require workarounds
• Backward compatibility lane preserves session semantics for pre-2026-07-28 clients until sunset date
• Deprecates Roots, Sampling, Logging, and HTTP+SSE with twelve-month removal floor (July 2027)
• Provides conformance suite and feature lifecycle policy to prevent future breaking changes

Organizations should migrate existing MCP servers to 2026-07-28 to achieve cost savings, improved reliability, and native serverless support while maintaining backward compatibility during transition periods.