Skip to content

Commit ff4bf50

Browse files
Document clientCapabilities persistence in WorkerTransport
Updates documentation to reflect that WorkerTransport now persists client capabilities across serverless restarts. This fixes an issue where elicitation and other capability-dependent features would fail after hibernation or cold starts. Changes: - Add initializeParams to TransportState interface documentation - Document that client capabilities are persisted and restored - Clarify the behavior of state restoration Related to cloudflare/agents#783 Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
1 parent e6a5a43 commit ff4bf50

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

src/content/docs/agents/model-context-protocol/mcp-handler-api.mdx

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -390,6 +390,12 @@ interface TransportState {
390390
initialized: boolean;
391391
initializeParams?: InitializeRequestParams;
392392
}
393+
394+
interface InitializeRequestParams {
395+
capabilities: ClientCapabilities;
396+
clientInfo: { name: string; version: string };
397+
protocolVersion: string;
398+
}
393399
```
394400

395401
The `TransportState` interface defines what gets persisted to storage:

0 commit comments

Comments
 (0)