You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -116,6 +116,15 @@ The server provides the following notification methods:
116
116
-`notify_progress` - Send a progress notification for long-running operations
117
117
-`notify_log_message` - Send a structured logging notification message
118
118
119
+
#### Session Scoping
120
+
121
+
When using Streamable HTTP transport with multiple clients, each client connection gets its own session. Notifications are scoped as follows:
122
+
123
+
-**`report_progress`** and **`notify_log_message`** called via `server_context` inside a tool handler are automatically sent only to the requesting client.
124
+
No extra configuration is needed.
125
+
-**`notify_tools_list_changed`**, **`notify_prompts_list_changed`**, and **`notify_resources_list_changed`** are always broadcast to all connected clients,
126
+
as they represent server-wide state changes. These should be called on the `server` instance directly.
127
+
119
128
#### Notification Format
120
129
121
130
Notifications follow the JSON-RPC 2.0 specification and use these method names:
0 commit comments