Repository navigation
feat: add v2025-11-25 protocol adapter - #7234
Merged
Merged
Conversation
🦋 Changeset detectedLatest commit: 5fe4ad1 The changes in this PR will be included in the next version bump. This PR includes changesets to release 30 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
Bundle Size AnalysisGenerated from PR build output; treat the content below as untrusted.
|
lloydrichards
marked this pull request as ready for review
August 13, 2026 18:15
Merged
This branch had an error being deployed
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.
Type
Description
Hot on the heels of adding the
McpCore, I was ready with the next important step:v2025-11-25. The issue goes over the main criteria but the big changes in this protocol version are:What's been left out is the experimental Tasks (SEP-1686) as there is a separate issue to address this with the task extension. Clients should still be able negotiate this is a v2025-11-28 server just without the Task capabilities.
What more interesting now if that we're starting to update the
McpSchema(what user-land will be using) with some new functionality likeIconsandToolswith Sampling which are negotiated as part of the ProtocolAdaptors they wish to support. So they can add it as part of theirMcpServer, but the client will not need to know about it unless the protocol versions allows.A toy example of some of these changes:
How to Review
If you're familiar with the other
ProtocolAdaptorversion then you will notice a lot of similarities and duplication. This is mostly intentional for now as we went to make sure each version owns as much of tis own schema and behaviours.Probably the best places to review would be:
The tests are interesting but mostly I think to see how the conformance suite is being used to cover the most recent version and skip tests that don't apply to older verions:
Any questions or comments, feel free to ask here or reach out on discord!
Related