Reland outbound MCP client on SDK v2 (spec 2026-07-28) - #1733
Merged
Conversation
Contributor
Cloudflare previewTorn down — the PR is closed. |
RhysSullivan
marked this pull request as ready for review
August 25, 2026 17:47
This was referenced Aug 25, 2026
Merged
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Reverts #1692, restoring #1591: remote Streamable HTTP connections auto-negotiate the 2026-07-28 protocol era, stdio opt-in negotiation (#1646) comes back with it, and the negotiated era is recorded on handshake spans.
The v2 client package was implicated in the Aug 19 latency incident (isolate reuse collapse). The isolate instrumentation from #1698 is now on main, so this deploy doubles as the planned production canary: monitoring p50 / cold-start rate after merge, rolling back via wrangler if reuse collapses again.