[Question]: Timeline for Streamable HTTP support in MCP Host Mode

[eeerie]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (Language Policy).
• Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) (Language Policy).
• Please do not modify this template :) and fill in all the required fields.

Describe your problem

According to the RAGFlow documentation, the Streamable HTTP transport is currently not supported in MCP Host Mode. The documentation states:

"If you set mcp-mode to host, you must add the --no-transport-streamable-http-enabled flag, because the streamable-HTTP transport is not yet supported in host mode."

Reference: https://ragflow.io/docs/launch_mcp_server

Since the legacy HTTP + SSE transport has been officially deprecated in favor of Streamable HTTP, this limitation creates a challenge for deployments that require Host Mode.

Questions

1. Is there a planned timeline for Streamable HTTP support in MCP Host Mode?
2. What are the technical blockers preventing this feature from being implemented in Host Mode?
3. Is there a roadmap issue or feature request tracking this improvement?

Context

Other users have raised concerns about this limitation in related issues (e.g., #10949).

Expected behavior

Streamable HTTP should be available as a transport option in both Self-Host Mode and Host Mode to ensure consistency and align with the deprecation of the legacy SSE transport.

[dosubot]

Hi @eeerie! I'm Dosu and I’m helping the ragflow team.

There’s currently no published timeline or roadmap for Streamable HTTP support in MCP Host Mode. The documentation and multiple issues confirm that this transport is not supported in Host Mode and must be disabled with the --no-transport-streamable-http-enabled flag source. While support is described as “planned but currently unavailable,” there are no technical blockers or architectural notes documented in the codebase or public issues, and no recent pull requests address this feature source. The main open question tracking this topic is issue #12934, which is the best place to watch for future updates. Users have raised concerns about deployment challenges, especially in Kubernetes environments, but maintainers have not provided implementation details or a timeline source.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[yongtenglei]

Hi @eeerie

Thank you for pointing this out. Done in this PR.

Cheers.