Repository navigation
Fix MCP connection renewal discovery - #48
Merged
Merged
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
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.
RolePatch connections could work initially and fail when the five-minute access token expired because deployed MCP clients requested only the advertised
resumescope. Advertiseoffline_accessin the two MCP protected-resource documents and MCP 401 challenges so clients request renewal through explicit consent.Provider metadata fields, headers, status and bodyless HEAD responses pass through.
/api/resumeand 403 challenges retain their existing scopes. Token lifetime, PKCE, owner/session checks and refresh issuance remain provider-controlled. The existing OAuth runbook records the bounded compatibility exception for deployed clients.Validation:
pnpm qualitypassed, including 820 passing tests and one opt-in skipped test, coverage, TypeScript, lint, docs and code-health checks.pnpm cf:buildpipeline completed through Next, OpenNext, static cache population and the Astro overlay.Production ChatGPT reconnection and a post-expiry tool call will be verified separately after release.