Add mcp_proxy for bidirectional message forwarding#1778
Closed
Add mcp_proxy for bidirectional message forwarding#1778
Conversation
Adds a convenience function for proxying messages between two MCP transports, enabling bidirectional message forwarding with proper error handling. Features: - Bidirectional forwarding between client and server transports - Optional error callback (sync or async) for exceptions on streams - Graceful handling of closed/broken streams - Clean shutdown on context exit This is a simpler reimplementation of the proxy pattern from #1711/#1763, addressing all review feedback.
9 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds a convenience function for proxying messages between two MCP transports, enabling bidirectional message forwarding with proper error handling.
Motivation and Context
This implements issue #12 - porting the TypeScript proxy pattern to Python. It's a simpler reimplementation of #1711/#1763 that addresses all review feedback from those PRs.
Key differences from #1763:
pragma: no cover- all code paths are testedanyio.Eventfor synchronizationHow Has This Been Tested?
13 unit tests covering:
All tests pass with
pytest-xdistparallel execution.Breaking Changes
None - this is a new feature.
Types of changes
Checklist
Additional context
Closes #12
Related PRs: #1711, #1763
AI Disclaimer