-
Notifications
You must be signed in to change notification settings - Fork 0
AIML-2969 Feature/internal/mcp transport context for http servlet sse server transport provider #6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AIML-2969 Feature/internal/mcp transport context for http servlet sse server transport provider #6
Conversation
…rovider and HttpServletStreamableServerTransportProvider
…d Jenkinsfile for builds
<artifactId>mcp-parent</artifactId> | ||
<version>0.12.0-SNAPSHOT</version> | ||
<version>0.12.0-sprout</version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: why not SNAPSHOT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@david-huber actually i wasn't sure if we even can or should push SNAPSHOT into nexus. I am thinking this should just be 0.12.0
or 0.12.0-rc1
or something?
12f49fb
to
7a4e9b9
Compare
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