Description
Expected Behavior
In the latest protocol version, we’ve introduced streamable HTTP transport with support for stateless sessions. Given this, I’ve been wondering whether it might now be feasible to implement the /mcp endpoint using a traditional REST API approach.
Current Behavior
I see that there’s already ongoing work in this repository to add streamable HTTP support. However, it’s not yet clear how I could implement the /mcp endpoint as a traditional REST API.
Our goal is to expose certain functionality over /mcp and host the server remotely, so that the client side doesn’t need to run a local mcp server. These functionalities are more like tools — they are stateless and don’t require a session. Also there is no need for server to send notification to client.
Currently, the SDK appears tightly coupled to javax.servlet.http.HttpServletRequest and HttpServletResponse. We're exploring whether it's possible to implement it using a different web framework, such as Vert.x.
This already appears to be possible in the Python SDK — I was able to successfully implement a stateless MCP API using FastAPI together with fastmcp. We're now exploring a Java-based solution because the Vert.x framework offers even higher performance.