2025-03-26 release #232
Merged
2025-03-26 release #232
Conversation
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
dsp-ant
approved these changes
Mar 26, 2025
|
FYI @modelcontextprotocol/sdk-maintainers, this new protocol revision is officially ready to go 🥳 |
|
When can we expect it to be officially released and bumped? |
|
@orliesaurus Your question is answered in the PR body above. |
This was referenced Mar 26, 2025
|
@jspahrsummers great to see some major wins with this merge. Wondering if you folks can share your thinking on how you are viewing this proposal at this point: #205 given that we have gone forward with a somewhat different approach. |
jspahrsummers
pushed a commit
that referenced
this pull request
Apr 7, 2025
`asyncio.run` expects a coroutine, not a function.
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.
This PR marks the new 2025-03-26 version of the Model Context Protocol, moving it out of draft status. I've included a changelog document summarizing key changes from the previous version, and made some organizational changes to the docs to share common things that apply to all versions (like "how we do versioning").
The diff will be pretty useless—I recommend just checking out the branch and running
npm run serve:docs.To users and implementors: note that SDKs will adopt this version at their own pace, and the prior version of the spec may remain in use for an undetermined amount of time. The spec describes how clients and servers perform version negotiation with one another, permitting backwards and forwards compatibility.
I am purposely not introducing a new draft spec yet, as I want to review how we version these docs generally, and figure out if maybe we can use Git branches to establish separate tracks in future. We can discuss that outside of this PR.