Repository navigation
Use current OAuth headers for stateful MCP tool calls - #157
Merged
Ciniesta merged 1 commit intoOct 14, 2026
Merged
Conversation
carlesonielfa
approved these changes
Oct 14, 2026
Ciniesta
deleted the
Use-current-OAuth-headers-for-stateful-MCP-tool-calls
branch
October 14, 2026 13:05
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.
Description:
Stateful MCP servers captured the headers from the initialization request and reused them for subsequent tool calls. This caused downstream services to receive an expired bearer token even when the MCP client sent a refreshed token.
This change removes the captured headers and reads them from mcp_server.request_context.request for each tool invocation.
Validation:
Added test