feat(rmcp)!: upgrade integration to rmcp 3.4 - #372
Merged
Merged
Conversation
dependabot
Bot
added
dependencies
Bumps [rmcp](https://github.com/modelcontextprotocol/rust-sdk) from 2.2.0 to 3.4.0. - [Release notes](https://github.com/modelcontextprotocol/rust-sdk/releases) - [Changelog](https://github.com/modelcontextprotocol/rust-sdk/blob/main/release-plz.toml) - [Commits](modelcontextprotocol/rust-sdk@rmcp-v2.2.0...rmcp-v3.4.0) --- updated-dependencies: - dependency-name: rmcp dependency-version: 3.4.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/cargo/rmcp-3.4.0
branch
from
September 23, 2026 12:49
e68c6ad to
77b6d68
Compare
Adapt tool responses and configuration types, retain existing default-protocol behavior, and verify real modern MCP requests and MRTR through the adapter. BREAKING CHANGE: rmcp is a public dependency of agent-client-protocol-rmcp. Supplied services must migrate to rmcp 3.x; release the integration as 4.x while keeping the core ACP SDK on 2.x.
benbrandt
changed the title
benbrandt
enabled auto-merge (squash)
September 24, 2026 11:11
benbrandt
disabled auto-merge
September 24, 2026 11:18
benbrandt
enabled auto-merge (squash)
September 24, 2026 11:18
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
1 participant
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.
Summary
Upgrade the public rmcp dependency from 2.2.0 to 3.4.0, including the adapter/API and fixture changes needed to make the original dependency bump pass.
CallToolResponsefrom manual handlers, useServerConfig/ClientConfig, and remove obsoleteToolExecutionmetadata.ttlMs: 0,cacheScope: private) while preserving the existing default/legacy response shape.Release compatibility
Breaking for agent-client-protocol-rmcp: rmcp is a public dependency. Its next release must be 4.x for rmcp 3.x services; the core ACP SDK remains 2.x. Manifest version changes remain with release-plz. The migration guide, compatibility table, changelog and release-review note document this.
Rust MSRV remains 1.88.
Scope
This is the prerequisite for the latest-only MCP-over-ACP modernization tracked in agentclientprotocol/agent-client-protocol#2222. It does not change the unstable ACP wire lifecycle or claim full MCP conformance. The modern transport will target 2026-07-28 only; preserving the dependency integration's current behavior here is not a commitment to a legacy mode in that transport.
rmcp 3.4 implements the modern request model, but
ProtocolVersion::LATESTstill defaults to 2025-11-25. Modern callers must select 2026-07-28 explicitly and send per-request metadata.Validation
just test— full workspace/all features and doctests passed.cargo +1.88.0 check --workspace --all-targets --all-features --locked— passed.cargo clippy --all-targets --all-features --locked— passed.cargo hack check -p agent-client-protocol-rmcp --feature-powerset --no-dev-deps— all four combinations passed.cargo fmt --all -- --check,mdbook build,git diff --check— passed.The complete platform/feature CI matrix should pass before merge; do not bypass required checks.