Last 12 weeks · 13 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
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
Repository: modelcontextprotocol/transports-wg. Description: Transports Working Group Stars: 12, Forks: 8. Open PRs: 5, open issues: 0. Last activity: 2d ago. Community health: 100%. Top contributors: kurtisvg, pja-ant, markdroth, domdomegg.
During SEP-2243, one of the pieces of feedback from the Core Maintainers was: Can we find a way to standardize this proposal of mapping body parameters into the header? This seems like it can be useful for resources and other structures too. This doc is a brief summary of investigation into addressing the feedback.