fix: WorkerTransport doesn't persist clientCapabilities, breaking elicitation in serverless #27667
+32
−3
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.
Summary
Document the new client capabilities persistence feature in
WorkerTransportfrom cloudflare/agents PR #783.Changes
Updated
/agents/model-context-protocol/mcp-handler-api/documentation to reflect:initializeParamsfield inTransportStateinterface that stores client capabilities, clientInfo, and protocolVersioninitializeParamsfieldContext
The original PR (cloudflare/agents#783) fixed a critical bug where client capabilities were not persisted in serverless environments. This caused features like elicitation to fail after Durable Object/Agent hibernation.
The fix ensures that when using
WorkerTransportwith persistent storage, client capabilities are:This documentation update makes developers aware of this behavior and the new fields in
TransportState.Related PR