docs: mark SSE transport examples as deprecated #561
Merged
+46
−51
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SSE transport has been removed from newer versions of the MCP spec. Streamable HTTP is preferred as it is more reliable. Moves SSE examples to a collapsed details section at the bottom of the example list and removes them from the 'How to Run' section.
github-actions
bot
added
T-documentation
alexhancock
approved these changes
Nov 25, 2025
Collaborator
alexhancock
left a comment
alexhancock
left a comment
There was a problem hiding this comment.
LGTM
@domdomegg thoughts on timeline for full deletion?
Member
Author
@alexhancock I think we definitely could do this if you'd be open to it. SSE was removed from the spec quite some time ago now and I don't think anyone should be creating new SSE servers. I can see it being useful for people maintaining older SSE servers. But there might just not really be any (from Claude.ai traffic I don't think there are any popular rust SSE servers AFAIK). Again, up to you! Happy to put a PR up to remove if you think we can :) |
Collaborator
|
@domdomegg Yeah I am comfortable scorched-earthing SSE stuff now if you want - feels like time... If someone really wants to do SSE in rust they can rely on an older version of the package until they switch to streamable http. |
domdomegg
added a commit
that referenced
this pull request
Nov 25, 2025
SSE transport has been removed from the MCP specification in favor of streamable HTTP. This removes all SSE-specific transport code: - Remove `transport-sse-client` and `transport-sse-server` features - Remove `SseClientTransport` and `SseServer` types - Remove SSE-specific examples (`counter_sse`, `counter_sse_directly`) - Migrate auth examples from SSE to streamable HTTP - Update tests to remove SSE transport usage - Update documentation BREAKING CHANGE: The following have been removed: - `transport-sse-client` feature - `transport-sse-client-reqwest` feature - `transport-sse-server` feature - `SseClientTransport` type - `SseServer` type - `sse_client` and `sse_server` modules Users should migrate to streamable HTTP transport which provides equivalent functionality. See `StreamableHttpClientTransport` and `StreamableHttpService` for the replacement APIs. Ref: #561 (comment)
domdomegg
added a commit
that referenced
this pull request
Nov 25, 2025
SSE transport has been removed from the MCP specification in favor of streamable HTTP. This removes all SSE-specific transport code: - Remove `transport-sse-client` and `transport-sse-server` features - Remove `SseClientTransport` and `SseServer` types - Remove SSE-specific examples (`counter_sse`, `counter_sse_directly`) - Migrate auth examples from SSE to streamable HTTP - Update tests to remove SSE transport usage - Update documentation BREAKING CHANGE: The following have been removed: - `transport-sse-client` feature - `transport-sse-client-reqwest` feature - `transport-sse-server` feature - `SseClientTransport` type - `SseServer` type - `sse_client` and `sse_server` modules Users should migrate to streamable HTTP transport which provides equivalent functionality. See `StreamableHttpClientTransport` and `StreamableHttpService` for the replacement APIs. Ref: #561 (comment)
alexhancock
pushed a commit
that referenced
this pull request
Dec 2, 2025
SSE transport has been removed from the MCP specification in favor of streamable HTTP. This removes all SSE-specific transport code: - Remove `transport-sse-client` and `transport-sse-server` features - Remove `SseClientTransport` and `SseServer` types - Remove SSE-specific examples (`counter_sse`, `counter_sse_directly`) - Migrate auth examples from SSE to streamable HTTP - Update tests to remove SSE transport usage - Update documentation BREAKING CHANGE: The following have been removed: - `transport-sse-client` feature - `transport-sse-client-reqwest` feature - `transport-sse-server` feature - `SseClientTransport` type - `SseServer` type - `sse_client` and `sse_server` modules Users should migrate to streamable HTTP transport which provides equivalent functionality. See `StreamableHttpClientTransport` and `StreamableHttpService` for the replacement APIs. Ref: #561 (comment)
3 tasks
nazq
added a commit
to nazq/test_mcp_servers
that referenced
this pull request
Dec 8, 2025
BREAKING CHANGE: Remove SSE transport (/sse, /message endpoints) Changes: - Remove SSE transport - deprecated in MCP spec, removed in rmcp 0.11 - Add error module with thiserror for standardized error handling - Add clippy.toml for fine-grained lint configuration - Add Config builder pattern for fluent API - Enhance test helpers with start_with_auth() and test client utilities - Update documentation to reflect Streamable HTTP only refs: - modelcontextprotocol/rust-sdk#561 - modelcontextprotocol/rust-sdk#562
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
<details>section at the bottom of the example listSSE transport is less reliable than streamable HTTP and has been removed from newer versions of the MCP specification.