Session ID agnostic MCP server example

[reda2000-cyber]

Expected Behavior
A simple, stateless MCP server that can be deployed on a serverless platform (e.g., in the cloud).

Current Behavior
I’m currently using StreamableHttpServerTransportProvider, which extends HttpServlet. However, after deployment, I encounter a "session not found" error—likely due to the application running across multiple nodes without shared session state.

Context
In the TypeScript implementation, it's straightforward to make the server stateless by setting the sessionIdGenerator to undefined, effectively disabling session management. Is there an equivalent or similarly simple approach to disable session handling in the Java implementation?

[134130]

The lifecycle section on MCP docs requires the initialization for the client session, because clients have different capability.

I don't think this is common, so I wouldn't expect it from the SDK.

[bwangll]

I think it is needed.

[134130]

Also, the MCP protocol is already stateless, because of using Streamable HTTP transport, not WebSocket.

I think the title Session ID agnostic MCP server example might be correct.