Document deprecation of client edge transport classes #26328
+137
−0
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
Documents the deprecation of
SSEEdgeClientTransportandStreamableHTTPEdgeClientTransportclasses and provides migration guidance for users.Changes
Context
Related to cloudflare/agents#637 - This PR removed the custom edge transport implementations since the official MCP TypeScript SDK now supports Cloudflare Workers natively (as of summer 2024). The SDK now exports deprecated wrapper classes that log console warnings to guide users to update their imports.
Target Audience
Users who were directly importing and using these transport classes in custom MCP client implementations (advanced use case - most users rely on the automatic transport handling in
McpAgentandaddMcpServer()).Generated with Claude Code
Co-Authored-By: Claude [email protected]