Model Context Protocol
HTTP+SSE transport removal
Deprecated, no dateSubscribe to Model Context ProtocolShare
Model Context Protocol deprecated transport sse without a shutdown date. Calls relying on this transport will fail once the removal takes effect. This change specifically impacts implementations currently using transport sse.
Calls it hits
transport sse
What to use instead of these calls
Connect over Streamable HTTP at the endpoint the server documents, usually /mcp. Switching requires a team decision beyond changing an identifier, as Streamable HTTP works only if the target server supports it.
Streamable HTTP works only where the server serves it too, which the calling code does not tell: the team decides.
In Model Context Protocol's words
Reclassify the HTTP+SSE transport (deprecated since protocol version
Facts
- API
- Model Context Protocol
modelcontextprotocol.io - Kind
- Removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Model Context Protocol's own pages
Questions
When does this change take effect?
Model Context Protocol deprecated transport sse without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Model Context Protocol has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Model Context Protocol 1
-
SDK mcp streamablehttp_client from major 2Removal Stopped working
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.