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: docs/mcp-transports.md
+38-2Lines changed: 38 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -306,14 +306,50 @@ The RPC transport is minimal by design (~350 lines) and fully supports:
306
306
- Notifications (messages without `id` field)
307
307
- Automatic reconnection after Durable Object hibernation
308
308
309
+
### Configuring RPC Transport Server Timeout
310
+
311
+
The RPC transport has a configurable timeout for waiting for tool responses. By default, the server will wait **60 seconds** for a tool handler to call `send()`. You can customize this by overriding the `getRpcTransportOptions()` method in your `McpAgent`:
The timeout ensures that if a tool handler fails to respond (e.g., due to an infinite loop or forgotten `send()` call), the request will fail with a clear timeout error rather than hanging indefinitely.
345
+
309
346
### Advanced: Custom RPC function names
310
347
311
348
By default, the RPC transport calls the `handleMcpMessage` function. You can customize this:
0 commit comments