chore(deps): update rust crate rmcp to v3 - #3778
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/rmcp-3.x
branch
5 times, most recently
from
July 29, 2026 21:47
c51c3b5 to
a27e39c
Compare
renovate
Bot
force-pushed
the
renovate/rmcp-3.x
branch
from
July 30, 2026 04:49
a27e39c to
08154a6
Compare
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.
This PR contains the following updates:
1.0.0→3.0.0Release Notes
modelcontextprotocol/rust-sdk (rmcp)
v3.0.1Compare Source
Fixed
v3.0.0Compare Source
RMCP 3.0 adds support for MCP 2026-07-28. Review the protocol key changes and the RMCP 3.0 migration guide before upgrading from 2.x.
Breaking changes
Mcp-Session-Id, standalone GET stream, DELETE-based session termination, orLast-Event-IDresumption. RMCP creates a fresh handler per request, so persistent state must live outside the handler.stateful_modeis renamed tolegacy_session_modeand now only controls older protocol versions; custom SSE clients must also accept an optional session ID.initialize/notifications/initialized; each request carries the protocol version and client capabilities in_meta, and servers exposeserver/discover. RMCP clients opt into this lifecycle withserve_with_lifecycleandClientLifecycleMode::DiscoverorAuto; the existingserve()path remains available for legacy initialization.subscriptions/listenreplaces the standalone GET stream andresources/subscribe/resources/unsubscribe.ping,logging/setLevel, andnotifications/roots/list_changedare unavailable under 2026-07-28; RMCP retains their APIs for legacy protocol sessions.ServerHandler::call_tool,get_prompt, andread_resourcenow return MRTR-aware response enums. Manual handler implementations and exhaustiveServerResultmatches must handleInputRequiredResult, and result models carry an optionalresult_typefor legacy wire compatibility.io.modelcontextprotocol/tasksextension, including new task handlers, methods, andTaskManagerAPIs.MetaObject,RequestMetaObject, andNotificationMetaObject;Annotations::last_modifiedis nowOption<String>; and tool structured content accepts anyserde_json::Value.AuthorizationRequest; metadata discovery is renamed toresolve_metadataand returns provenance; and custom OAuth HTTP errors are now boxed source errors.What's Changed
issuerby @jamadeo in #1051issuerin authorization server metadata by default by @jamadeo in #1054New Contributors
Full Changelog: modelcontextprotocol/rust-sdk@rmcp-v2.2.0...rmcp-v3.0.0
v2.2.0Compare Source
Added
Fixed
v2.1.0Compare Source
Added
Fixed
v2.0.0Compare Source
Migration guide: https://redirect.github.com/modelcontextprotocol/rust-sdk/discussions/926
Added
Fixed
Other
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.