Repository navigation
fix(mcp): bump @modelcontextprotocol/sdk to 1.32.x - #1443
Merged
TheGreatAxios merged 3 commits intoOct 15, 2026
Merged
Conversation
1.32 flips transport redirects to same-origin-only; the three streamable-http transport sites set redirectPolicy "follow" because MCP endpoints are operator-configured (trust-on-first-use local entries) and 1.30 semantics should survive the bump. 1.31 binds stored oauth credentials to the authorization-server issuer: the refresh path now stamps and returns issuer-bound tokens so parked credentials re-stamp through the SDK contract instead of tripping the no-issuer deprecation on a legacy store. MCP SDK 2.x deferred until the upstream codemod for the rewritten provider/discovery APIs ships.
Contributor
|
Superseded by the comment below. |
Contributor
|
Superseded by the comment below. |
Contributor
|
Triage: Unsure A maintainer will review this pull request. |
TheGreatAxios
changed the base branch from
cl-10659-providerauth-pins-codex-provider-oauth-core-ws-remov
to
main
October 15, 2026 20:59
…132x-redirect-issuer-correct # Conflicts: # bun.lock # package.json
`redirectPolicy: "follow"` made SDK 1.32.1 follow 307/308 on OAuth discovery and token requests, so refresh tokens and auth codes could be posted off-origin. Omit the override and keep the SDK default.
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
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
@modelcontextprotocol/sdkbumps 1.30.0 → 1.32.1. The three streamable-HTTP client transport sites (auth retry, oauth:false, oauth flows) now pinredirectPolicy: "follow"— MCP endpoints are operator-configured with trust-on-first-use local entries, so pinning preserves the same-origin redirect semantics the SDK changed as a 1.32 default. No SSE sites exist (grep evidence).-oauth issuer correctness per 1.31+: stored OAuth tokens now stamp
issuer: authorizationServerUrlon the refresh path before persistence, so parked credentials re-bind via the SDK's key rather than tripping the "no issuer" deprecation warning on the next auth. Theauth-storeissuer-keyed handling is a comment-documented contract, not an enforced runtime gate (read-migration preserved: legacy stores load unstamped intentionally rather than guessing an issuer and discarding valid tokens on mismatch-throw).maxToolInputElementsdeclined by one-line reason in the PR body (repo is MCP-client-only, it's a server-only server-side option).Verification
bun run checkexit 0: 8950 pass / 0 fail across 580 files; src/mcp suites targeted (176 tests, 16 files) all green.authorizationServerUrlbinding key correctness viaString(URL)semantics, no PRM poisoning, legacy-store fallback semantics).redirectPolicyshape directly — a follow-up line pinned through the SDK contract and covered by the OAuth-flow grep evidence in the review; no code change required.Fixes CL-10653