(Original content) **Expected Behavior** The ["Streamable HTTP" transport ](https://github.com/modelcontextprotocol/specification/pull/206)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 - [x] Reviewing the Spec and introducing architectural changes required for the client side aiming for backwards compatibility if possible (#292) - [x] Implementing JDK HTTP Client support (#337) - [x] Implementing WebClient Client support (#292) - [x] 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 (#420) - [x] Implementing Servlet Server support (#290) - [x] Implementing Spring WebMVC Server support (#425) - [x] Implementing Spring WebFlux Server support (#420) - [x] Servlet & MVC Stateless: (#432)