Implemented Transport-Translation Bridge (mcpgateway.translate) #128
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.
📝 Pull Request Template Selection
Thank you for contributing! To help us review your pull request effectively, please select the appropriate template:
I have implemented the Transport-Translation Bridge (mcpgateway.translate) feature for the MCP Gateway.
Key Components Implemented:
1. Core Bridge Implementation
2. CLI Features
mcpgateway-translate
3. Docker Support
4. Testing & Quality
5. Documentation
User Stories Fulfilled:
✅ User Story 1:
mcpgateway-translate --stdio "uvx mcp-server-git" --port 9000
exposes stdio server over SSE✅ User Story 2:
mcpgateway-translate --sse "https://corp.example.com/mcp"
bridges remote SSE to local stdio✅ User Story 3: Health endpoint and CORS support with
--healthEndpoint /healthz --cors "https://app.example.com"
✅ User Story 4: Official Docker images with variants published to GHCR
Production-Ready Features:
The implementation is ready for production use and provides a first-class, batteries-included bridge for running any MCP stdio-based server or remote endpoint over every other official transport protocol.