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
The `server_context.report_progress` method accepts:
167
+
168
+
-`progress` (required) — current progress value (numeric)
169
+
-`total:` (optional) — total expected value, so clients can display a percentage
170
+
-`message:` (optional) — human-readable status message
171
+
172
+
#### Server-Side: Direct `notify_progress` Usage
173
+
174
+
You can also call `notify_progress` directly on the server instance:
175
+
176
+
```ruby
177
+
server.notify_progress(
178
+
progress_token:"token-123",
179
+
progress:50,
180
+
total:100, # optional
181
+
message:"halfway"# optional
182
+
)
183
+
```
184
+
185
+
**Key Features:**
186
+
187
+
- Tools report progress via `server_context.report_progress`
188
+
-`report_progress` is a no-op when no `progressToken` was provided by the client
189
+
-`notify_progress` is a no-op when no transport is configured
190
+
- Supports both numeric and string progress tokens
191
+
127
192
### Logging
128
193
129
194
The MCP Ruby SDK supports structured logging through the `notify_log_message` method, following the [MCP Logging specification](https://modelcontextprotocol.io/specification/latest/server/utilities/logging).
The server will send `notifications/progress` back to the client during execution.
1127
+
1054
1128
#### HTTP Authorization
1055
1129
1056
1130
By default, the HTTP transport layer provides no authentication to the server, but you can provide custom headers if you need authentication. For example, to use Bearer token authentication:
0 commit comments