pinning mcp as version 2 is not compatible - #3
Open
joelsmithucl wants to merge 1 commit into
Open
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
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.
I have found I need to pin the mcp version for using this mcp in Kiro due to the below from Claude AI
"This confirms the issue. The mcp Python SDK released v2 with major breaking changes. Your server code uses the v1 API style (from mcp.server import Server, @server.list_tools() decorator style, etc.), and since requirements.txt has no version pin, pip install mcp now installs v2 which is incompatible.
The migration guide explicitly says: "If your package depends on mcp, keep a <2 upper bound until you've migrated.""