[FEAT] added support for AuthInfo in extra for StreamableHTTPServerTransport #399
+165
−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
This was referenced Apr 24, 2025
|
We tested this on a POC implementing an stateless server with Streamable HTTP Transport and it worked perfectly. It's the missing piece that allowed us to test our approach for a stateless server supporting OAuth-based authentication end-to-end. Great work! |
|
I ran into the same issue yesterday, would be great if this change could be added! |
|
We would also appreciate release with this fix |
|
waiting for this change as well.. without this, we cannot pass the AuthInfo to the tools. |
|
also waiting for this feature |
|
@jerome3o-anthropic @dsp-ant Would it be possible for one of the maintainers to kindly review the PR? Thank you! |
|
waiting for this also 🙏 |
|
Waiting for this |
|
I really need this 🙏 |
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.
Includes the
req.authAuthInfo that's set by the MCP Server bearer auth middleware in the server request handler via Streamable HTTP Transport, allowing for distinguishing of users in requests (eg. tool use).Motivation and Context
Authorisation token passed through the client (MCP inspector) needs to be used by tools implemented by the server to make sure that they can get user specific data.
Implementation has been inspired from SSE Transport - #166
How Has This Been Tested?
Added unit tests ensuring:
Breaking Changes
None
Types of changes
Checklist
Additional context
Fixes #398