Repository navigation
fix(mcp): use initialize-compatible protocol - #412
Merged
Merged
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
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.
MCP servers that reject protocol revisions without an initialize handshake cannot connect when the client advertises the newest protocol revision during initialization.
Use
ClientConfigwithLATEST_WITH_INITIALIZEfor native connections, including caller-supplied HTTP clients and authentication probes. Require rmcp 3.5 or newer and refresh the lockfile. The existing JSON, SSE, and injected-client fixtures now reject revisions outside the initialize-era protocol set.Validation: Rust formatting completed. Tests are left to CI; no local builds or test runs.