modelcontextprotocol/typescript-sdk
Watch
1
0
Fork
You've already forked typescript-sdk
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
typescript-sdk/.changeset/use-scopes-supported-in-dcr.md
Paul Carleton 1a78b0138f
 feat: use scopes_supported from resource metadata by default (forward-port #757) (#1614) 
Co-authored-by: Anthony Giniers <antogyn@gmail.com>
2026-03-02 17:13:59 +00:00

752 B
Raw Blame History

@modelcontextprotocol/client
minor

Apply resolved scope consistently to both DCR and the authorization URL (SEP-835)

When scopes_supported is present in the protected resource metadata (/.well-known/oauth-protected-resource), the SDK already uses it as the default scope for the authorization URL. This change applies the same resolved scope to the dynamic client registration request body, ensuring both use a consistent value.

  • registerClient() now accepts an optional scope parameter that overrides clientMetadata.scope in the registration body.
  • auth() now computes the resolved scope once (WWW-Authenticate → PRM scopes_supported → clientMetadata.scope) and passes it to both DCR and the authorization request.