We are bringing back SSE
Written by punkpeye on .
The Change
About two months ago, we deprecated SSE in favor of Streamable HTTP. Later, we completely removed SSE for new servers. Today, we are bringing it back for all servers.
The reason we deprecated SSE was because we were expecting for the ecosystem to switch to Streamable HTTP. However, after surveying the ecosystem, we found that most of the clients still only support SSE.
In fact, when we surveyed paying Glama customers about the features they would most want us to support, SSE was surprisingly the second most requested feature (led only by OAuth). While this was a small sample of just 100 select clients, we believe it accurately represents the current state of affairs.
How to Connect
Moving forward, every server is accessible via SSE and Streamable HTTP.
If you are an existing user of Streamable HTTP, you can continue to use the Streamable HTTP endpoint. Both endpoints are functionally equivalent with identical logging, performance, and features.
The streamble HTTP/SSE url is available under https://glama.ai/settings/mcp/servers
Our Commitment
Since we have already done the grunt work needed to support both transports in parallel, we are committing to support both transports indefinitely into the future. Therefore, if you require SSE transport, that's now available to you.
If your client supports Streamable HTTP, we encourage you to prefer the Streamable HTTP endpoint as it is the MCP specification's preferred transport. SSE has beenofficially deprecated in the spec, though we will continue supporting it for backward compatibility.
Written by punkpeye (@punkpeye)