mcp: adopt sep-1699 reconnection behavior#276953
Merged
connor4312 merged 1 commit intomainfrom Nov 12, 2025
Merged
Conversation
Contributor
📬 CODENOTIFYThe following users are being notified based on files changed in this PR: @TylerLeonhardtMatched files:
|
Tyriar
approved these changes
Nov 12, 2025
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adopts the SEP-1699 reconnection behavior for MCP (Model Context Protocol) HTTP connections, implementing server-controlled retry timing for SSE (Server-Sent Events) backchannel reconnections.
Key Changes:
- Implements server-specified retry timing via SSE
retrydirective, allowing servers to control reconnection delays - Adds defensive check for empty message data before processing SSE events
- Maintains backward compatibility with exponential backoff when server doesn't specify retry timing
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Refs modelcontextprotocol/modelcontextprotocol#1783