Issues with MCP Server Integration and State Loss in Dust

Hi, Wouter from Tally here 👋 We had some users reach out that they're having trouble getting our MCP server to work with Dust. However, after investigating, I see that state gets lost because for some reason Dust tries to re-initialize after every tool call. Since our MCP server is stateful (form building, you iterate on a form) it will indeed fail to build a form and save it eventually. What we see is that after it successfully made a tool call with POST /mcp the request still included the Mcp-Session-Id. Then it does a GET /mcp call – which still includes the Mcp-Session-Id, and then it will make a POST /mcp call without the Mcp-Session-Id and freshly initialize (and get a new Mcp-Session-Id back) – while we return the Mcp-Session-Id on every request made. Can someone shed some light on this? Don't know if there's a better channel for discussing technical / integration topics. I've looked at your docs page but I don't see anything mentioned about state. For your reference, the MCP spec about session management.