fix(plugin-mcp): pin modelcontextprotocol/sdk dependency version to 1.24.0 #15017
+15
−20
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
jonathanelmgren
changed the title
jonathanelmgren
changed the title
DanRibbens
approved these changes
Dec 30, 2025
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.
Summary
Pins
@modelcontextprotocol/sdkto~1.24.0to avoid breaking changes in 1.25.x that cause 406 errors in the MCP plugin.Problem
The current dependency declaration
^1.17.2allows installation of@modelcontextprotocol/sdk@1.25.x, which introduced breaking changes in theWebStandardStreamableHTTPServerTransportthat cause the MCP plugin to fail with 406 "Not Acceptable" errors.Solution
Change the dependency to use
~1.24.0(tilde) instead of^1.17.2(caret), restricting updates to patch versions only (1.24.x).Changes
packages/plugin-mcp/package.json: Update SDK version from^1.17.2to~1.24.0Breaking Changes
None - this prevents a breaking change from affecting users.
Follow-up
Once the @modelcontextprotocol/sdk team releases a fixed version or documents the correct usage pattern for 1.25.x+, we can update to allow newer versions.
closes: #15016
closes: #14952