fix(oauth): pass bearer token to all streamable http requests #476
+17 −6
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
github-actions bot added T-core There was an errant typo in the CHANGELOG that is breaking CI
gpeal force-pushed the gpeal/add-auth-to-streamable-http-2 branch from 6ddf259 to 79548e2 Compare 
| Aligns with my understanding
per https://modelcontextprotocol.io/specification/draft/basic/authorization#token-requirements |
alexhancock approved these changes Oct 7, 2025
Merged
| @gpeal thank you very much for this fix, our MCP wasn't working properly and was planning to dig into |
gpeal added a commit to openai/codex that referenced this pull request Oct 21, 2025
[Release notes](https://github.com/modelcontextprotocol/rust-sdk/releases) Notably, this picks up two of my PRs that have four separate fixes for oauth dynamic client registration and auth modelcontextprotocol/rust-sdk#489 modelcontextprotocol/rust-sdk#476
JeffCarpenter pushed a commit to JeffCarpenter/codex that referenced this pull request Oct 24, 2025
[Release notes](https://github.com/modelcontextprotocol/rust-sdk/releases) Notably, this picks up two of my PRs that have four separate fixes for oauth dynamic client registration and auth modelcontextprotocol/rust-sdk#489 modelcontextprotocol/rust-sdk#476
Holovkat pushed a commit to Holovkat/codex-pro that referenced this pull request Oct 29, 2025
[Release notes](https://github.com/modelcontextprotocol/rust-sdk/releases) Notably, this picks up two of my PRs that have four separate fixes for oauth dynamic client registration and auth modelcontextprotocol/rust-sdk#489 modelcontextprotocol/rust-sdk#476
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 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.
Motivation and Context
The auth token wasn't passed to all endpoints which causes 401s in some MCP servers such as GitHub's.
I also clarified that the auth header should be just the bearer token rather than the full header value.
It is possible that some clients were passing in the wrong value here (like Codex)
Please confirm that this is the expected behavior.
How Has This Been Tested?
I was able to repro the GitHub MCP 401 and confirm that it works after this change
Codex:
Breaking Changes
None.
Types of changes
Checklist
Additional context
I wrote the core code by hand (it also matches #464) but codex wrote the tests.
Fixes #464