Last 12 weeks · 12 commits
5 of 6 standards met
Very early draft, will demo and tidy-up for feedback/development. Motivation and Context How Has This Been Tested? Breaking Changes Types of changes [ ] Bug fix (non-breaking change which fixes an issue) [ ] New feature (non-breaking change which adds functionality) [ ] Breaking change (fix or feature that would cause existing functionality to change) [ ] Documentation update Checklist [ ] I have read the MCP Documentation [ ] My code follows the repository's style guidelines [ ] New and existing tests pass locally [ ] I have added appropriate error handling [ ] I have added or updated documentation as needed Additional context
Repository: modelcontextprotocol/transports-wg. Description: Transports Working Group Stars: 11, Forks: 7. Open PRs: 5, open issues: 0. Last activity: 2d ago. Community health: 100%. Top contributors: kurtisvg, pja-ant, markdroth, domdomegg.
This is a draft SEP for Multi Round-Trip Requests (MRTR). Motivation and Context See SEP for details. How Has This Been Tested? Not tested yet, that will happen when we implement. Breaking Changes See SEP for details. Types of changes [ ] Bug fix (non-breaking change which fixes an issue) [x] New feature (non-breaking change which adds functionality) [x] Breaking change (fix or feature that would cause existing functionality to change) [ ] Documentation update Checklist [x] I have read the MCP Documentation [x] My code follows the repository's style guidelines [x] New and existing tests pass locally [x] I have added appropriate error handling [x] I have added or updated documentation as needed Additional context N/A
Motivation and Context This PR introduces a SEP for incorporating HTTP features into the HTTP Transport that support processing by "middle boxes" on the internet, for tasks like routing, tracing, and priorization. How Has This Been Tested? I have a reference implementation built on the C# SDK that illustrates the basic features in this SEP. https://github.com/mikekistler/csharp-sdk/tree/mdk/http-standardization Breaking Changes All changes are gated by protocol version and thus not breaking. Types of changes [ ] Bug fix (non-breaking change which fixes an issue) [x] New feature (non-breaking change which adds functionality) [ ] Breaking change (fix or feature that would cause existing functionality to change) [ ] Documentation update Checklist [x] I have read the MCP Documentation [x] My code follows the repository's style guidelines [ ] New and existing tests pass locally [ ] I have added appropriate error handling [ ] I have added or updated documentation as needed Additional context This PR is primarily to allow comment and discussion within the Transports Work Group.