Record the MCP-over-ACP method decision as blocked upstream - #42
Merged
Merged
Conversation
Issue #39 asked for the shape decision to be recorded before any code. The binding will be a standard-library message mover with no third-party MCP SDK, matching the rmcp won't-port rationale. Implementation is blocked: agentclientprotocol/agent-client-protocol#2223 replaced the pinned connection-based draft (mcp/connect, mcp/message, mcp/disconnect) with request-scoped mcp/message for MCP 2026-07-28, and no schema release includes it yet. Per the pin workflow, work resumes once the Rust SDK pins a schema that does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QgVQ6ZTTKi3zEMaYkm4pWr
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
2 participants
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.
Refs #39. This PR records the design decision #39 asked for before any code is written, and notes that implementation is waiting on an upstream schema release.
Problem
#39 asks for native MCP-over-ACP support (
mcp/connect,mcp/message,mcp/disconnect) and wants the design recorded before any code. Upstream has since changed the design. agentclientprotocol/agent-client-protocol#2223 (merged Sep 25) replaced the connection-based draft that ourschema-v1.23.0/schema-v2.0.0-alpha.5pins model with a request-scopedmcp/messagebinding for MCP 2026-07-28.mcp/connectandmcp/disconnectare gone from the v1 and v2 unstable schemas on upstreammain, and the RFD says the earlier drafts "are not compatibility commitments". No schema release includes the change yet.Change
Documentation only:
docs/unstable-facades.md: the "still open" note becomes a section that:agent-client-protocol-rmcpis won't port;mcpandv2/mcp.ROADMAP.md: the remaining-gap entry now says the shape is decided and the work is blocked upstream.CHANGELOG.md: adds an Unreleased entry.The cookbook comments that mention
mcp/connect/mcp/disconnectare left as they are. They describe the pinned schema accurately and still point at #39.Validation
docs/schema-pin-workflow.mdanddocs/unstable-facades.mdexist, and the pin-workflow wording matches its "move only when the Rust SDK moves its exact pin" trigger.main:schema/v1/schema.unstable.jsonandschema/v2/schema.unstable.jsoncontain onlymcp/message, plusMcpRequestIdandMcpError.schema-v1.23.0andschema-v2.0.0-alpha.5(Sep 18) are still the newest.Remaining limits
#39 stays open. Once a schema release and a Rust SDK pin include agentclientprotocol/agent-client-protocol#2223, the issue should be rescoped to the request-scoped binding. The details are in the issue comment.
🤖 Generated with Claude Code
https://claude.ai/code/session_01QgVQ6ZTTKi3zEMaYkm4pWr
Generated by Claude Code