Open
Description
(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
- 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
- Implementing Servlet Server support
- Implementing Spring WebMVC Server support
- Implementing Spring WebFlux Server support
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Todo