Support server to client notifications from the stateless transport #472
+299
−34
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
Randgalt
force-pushed
the
joranz/support-stateless-notifications
branch
2 times, most recently
from
efd322f to
fdb7799
Compare
Randgalt
commented
Aug 8, 2025
| * @param method notification method name | ||
| * @param params any parameters or {@code null} | ||
| */ | ||
| default void sendNotification(String method, Object params) { |
There was a problem hiding this comment.
An alternative to this might be a separate McpNotifier instance that would be accessed by calling McpTransportContext.get() with a lib-defined key. wdyt?
Randgalt
force-pushed
the
joranz/support-stateless-notifications
branch
from
fdb7799 to
27ef5a6
Compare
The MCP spec allows stateless servers to send notifications to the client during a request. The response needs to be upgraded to SSE and the notifications are send in a stream until the final result is sent. This commit adds a `sendNotification` method to the transport context allowing each transport implementation to implement it or not. In this commit, HttpServletStatelessServerTransport implements the method and when the caller first sends a notification, the response is changed to `TEXT_EVENT_STREAM` and events are then streamed until the final result. This change will allow future features such as logging, list changes, etc. should we ever decide to support sessions in some manner. Even if we don't support sessions, sending progress notifications is a useful feature by itself.
Randgalt
force-pushed
the
joranz/support-stateless-notifications
branch
from
27ef5a6 to
3f83ef2
Compare
|
@tzolov do you have plans to support sessions for the stateless transport/server? We have some ideas that we will likely implement in our own code but could contribute here if there's interest. |
|
Noe: I've only done |
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.
The MCP spec allows stateless servers to send notifications to the client during a request. The response needs to be upgraded to SSE and the notifications are send in a stream until the final result is sent.
This commit adds a
sendNotificationmethod to the transport context allowing each transport implementation to implement it or not. In this commit, HttpServletStatelessServerTransport implements the method and when the caller first sends a notification, the response is changed toTEXT_EVENT_STREAMand events are then streamed until the final result.This change will allow future features such as logging, list changes, etc. should we ever decide to support sessions in some manner. Even if we don't support sessions, sending progress notifications is a useful feature by itself.
Motivation and Context
We would like to have support for progress notifications in the stateless implementation.
How Has This Been Tested?
testNotifications()added toHttpServletStatelessIntegrationTestsBreaking Changes
none
Types of changes
Checklist