fix(mcp): send custom headers regardless of OAuth settings#5273
Merged
Conversation
Previously, custom headers (e.g., Bearer tokens) were only sent when
oauth was explicitly set to false. This caused a regression where
configs like:
{
"type": "remote",
"url": "...",
"headers": { "Authorization": "Bearer ..." }
}
would fail because headers weren't being sent on the initial request.
Now headers are always sent when provided, regardless of OAuth settings.
edevil
force-pushed
the
fix_oauth_regression
branch
from
5f1c7da to
5a23ebb
Compare
xywsxp
pushed a commit
to xywsxp/opencode
that referenced
this pull request
Apr 24, 2026
…#5273) Co-authored-by: Aiden Cline <63023139+rekram1-node@users.noreply.github.com>
Rwanbt
pushed a commit
to Rwanbt/opencode
that referenced
this pull request
May 5, 2026
…#5273) Co-authored-by: Aiden Cline <63023139+rekram1-node@users.noreply.github.com>
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
2 participants
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.
Previously, custom headers (e.g., Bearer tokens) were only sent when oauth was explicitly set to false. This caused a regression where configs like:
{
"type": "remote",
"url": "...",
"headers": { "Authorization": "Bearer ..." }
}
would fail because headers weren't being sent on the initial request.
Now headers are always sent when provided, regardless of OAuth settings.