Support MCP streamableHttp transport for MCP clients and MCP servers

Feature Requests
1

The idea is:

Support MCP streamableHttp transport for clients and servers

My use case:

I have an MCP server that only supports streamableHttp transport (the new standard that replaces SSE)

I think it would be beneficial to add this because:

SSE is deprecated. StreamableHttp transport is a key enabler for remote servers and enterprise use-cases.

Any resources to support this?

see “DEPRECATED” note https://mcp-framework.com/docs/Transports/sse/
stream transport https://mcp-framework.com/docs/Transports/http-stream-transport

Are you willing to work on this?

No - you wouldn’t want me to.

2

Thanks for raising this, you got my vote, SSE is going to be deprecated, so I would really want to see StreamableHTTP transport to be implemented

4 Likes
3

I just encountered an http streamable only mcp server as well.

1 Like
4

Same here as well . Did not find any solution but based on this Add support for HTTP Streamable Transport we might be in luck soon.

5

use v1.99.0

6

1.99.0 isnt available in docker registry using the specific version or unstable next release

1 Like
7

v1.99.0 only supports streamable http for the mcp server node afaik. Streamable http still is not supported on the mcp client node, which is what was asked here

1 Like
8

Up! Actually the node MCP Client doesn’t support streamable-http, just server sent events…

ironically, the MCP Server can exposes both of them as trigger :smiley:

9

(post deleted by author)