docs: clarify requiresOAuth applies to all remote MCP transports, not just sse#589
Open
Educg550 wants to merge 1 commit into
Open
docs: clarify requiresOAuth applies to all remote MCP transports, not just sse#589Educg550 wants to merge 1 commit into
requiresOAuth applies to all remote MCP transports, not just sse#589Educg550 wants to merge 1 commit into
Conversation
|
@Educg550 is attempting to deploy a commit to the LibreChat's projects Team on Vercel. A member of the Team first needs to authorize it. |
5 tasks
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.
The
requiresOAuthoption was documented asssetype only, but it lives in the shared base MCP options schema and is honored at runtime for every URL-based transport (sse,streamable-http,websocket). This PR corrects the type annotation and notes accordingly, and adds guidance thatrequiresOAuth: falseshould be set for servers protected only by a staticAuthorizationheader (e.g. a Bearer API key) — since startup auto-detection probes the server without the configured headers and can misclassify such a server as OAuth-protected when it answers with a401/WWW-Authenticate: Bearerchallenge.