Stateful Session Support & Strategy

[stpforotx-ui]

Hello Team,
The latest MCP specification removes protocol-level sessions. With ContextForge, what is the roadmap for existing servers that rely on session features like session pooling? Will support for stateful sessions continue in upcoming releases, and would you recommend/encourage teams to keep using stateful session support moving forward?

Thanks in advance for your guidance!

[gcgoncalves]

Hi, @stpforotx-ui, thanfor for your interest on the project! We're aware of the MCP protocol updates and preparing for them. Look at our plan for version 1.1 and for version 2.0, particularly at the issue #6218 for version 1.1.

In short, session will remain supported, but from version 2.0 the plan is to NOT persist the sessions:

The data plane connects to any MCP server that conforms to the "dual-era" compatibility outline as defined in [https://modelcontextprotocol.io/specification/2026-07-28/basic/versioning#backward-compatibility-with-initialization-based-versions]. Exception: Sessions from stateful-era servers will not be persisted; it is to be assumed any connection to those servers is "fire and forget"