SSE is deprecated, please switch MCP server to streamable-http

[antonkulaga]

I noticed in the inspector:
New SSE connection. NOTE: The sse transport is deprecated and has been replaced by streamable-http"

Please, update the library to generate streamable-http. If it is not planned let us know (will have to switch to another MCP library then).

[yxj1028530975]

Is this project still supported?

[mpereira]

For folks looking for alternatives, jlowin/fastmcp supports streamable-http.

[easyservices]

For folks looking for alternatives, jlowin/fastmcp supports streamable-http.

Not the same scope as fastmcp does not turn existing APIs into MCP tools, as far as I know.

[mpereira]

For folks looking for alternatives, jlowin/fastmcp supports streamable-http.

Not the same scope as fastmcp does not turn existing APIs into MCP tools, as far as I know.

Check it out in the README.

https://gofastmcp.com/patterns/fastapi

[mcfredrick]

I'm hoping this project isn't dead. I've tried FastMCP as an alternative. It may work for simple services. But it doesn't play well with FastAPI dependency injection and requires a lot more code to work around that and other issues.

I would much prefer to use this project but SSE doesn't play nicely with kubernetes. So, Streamable HTTP is a must.

[tori-tadata]

Hey, this is Tori from the Tadata team. I’ve been using the downgrade workaround myself. We definitely plan to keep maintaining the project — we've just been a bit heads-down preparing to launch some new capabilities. Appreciate your patience, and apologies for the delay! @yxj1028530975 @mcfredrick

[mcfredrick]

Thanks for the update @tori-tadata. I'm glad to hear things are moving along. I'm cool with using the downgrade workaround for continued prototyping as long as there's probably going to be Streamable HTTP in the future. I'll keep watching this repo. Thanks again!

[jshcrm]

Hey @tori-tadata! When you say you plan to keep maintaining the project but your heads-down preparing to launch new capabilities are you saying that youre on another project and will come back to this or that this is actively being worked on? I'm on the fence about whether I should bake my own streamable-http solution or wait for this library to catch up, as I have a somewhat immediate need for streamable-http. Curious about a rough timeline, if thats possible, on when this might be implemented. I'd also be willing to take a crack at it myself with a PR on this project if you guys aren't already in progress on that.

[de-code]

This seems to be a duplicate of #61