Open
Description
Hello, we are trying to implement an MCP server and deploy in a distributed system, but we have found that session management is done in memory in the application instance.
I was wondering if this is a correct assumption, and if so, if there are any plans to abstract this behavior in a way that a client using an streamable http server would "simply" connect to another instance of the same server running, and while the session ID is still valid continue the same interaction.
Metadata
Metadata
Assignees
Labels
No labels