(Original content)
Expected Behavior

The "Streamable HTTP" transport is a fantastic feature, particularly beneficial for stateless MCP servers and remote MCP servers in distributed scenarios. It enables MCP to be swiftly employed in production-grade agent applications

Current Behavior

The issue with the current session is that it needs to support distributed sessions.

(Edit by @chemicL follows)

To split the task, what needs to happen to consider it done:

Steps

• Reviewing the Spec and introducing architectural changes required for the client side aiming for backwards compatibility if possible (WebClient Streamable HTTP support #292)
• Implementing JDK HTTP Client support (feat: implement HttpClient Streamable HTTP transport #337)
• Implementing WebClient Client support (WebClient Streamable HTTP support #292)
• Reviewing the Spec and introducing architectural changes required for the server side aiming for backwards compatibility if possible and allowing both stateful and stateless servers (Streamable HTTP Server abstractions and WebFlux transport provider #420)
• Implementing Servlet Server support (HttpServlet Streamable HTTP server implementation #290)
• Implementing Spring WebMVC Server support (feat: Add Spring WebMVC streamable server transport provider #425)
• Implementing Spring WebFlux Server support (Streamable HTTP Server abstractions and WebFlux transport provider #420)
• Servlet & MVC Stateless: (feat: add WebMVC and HttpServlet stateless server transports #432)