Feature/mcp transport context for http servlet sse server transport provider #5
+134
−11
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.
NOTE: this is also a pending PR to upstream (modelcontextprotocol#477), but we can't wait.
Implements modelcontextprotocol#476.
Motivation and Context
modelcontextprotocol#420 introduced McpTransportContext.
McpTransportContext
should be supported inHttpServletSseServerTransportProvider
to enable those who are still on that transport to leverageMcpTransportContext
to set attributes that Tools, etc. have access to. This is crucial for implementing Authentication & Authorization at the Tool level.Current Behavior
McpTransportContext
is absent fromHttpServletSseServerTransportProvider
Context
How has this issue affected you?
We're not able to switch to
HttpServletStreamableServerTransportProvider
yet, but wish to useMcpTransportContext
instead of our custom built similar capability.What are you trying to accomplish?
Authn/z at Tool level.
How Has This Been Tested?
HttpServletSseServerTransportProvider
HttpServletSseServerTransportProvider
Breaking Changes
No, use of the
McpTransportContext
is optional.Types of changes
Checklist
Additional context
None