fix: restore MCP SDK v1 client compatibility - #242
Merged
Conversation
Replace the SDK v2 beta client/server packages with the SDK v1 client path, keep the new compatibility coverage, and raise the SDK floor to ^1.30.0 for existing lockfiles. Preserve direct zod packaging and the close ownership fix already merged on main.
This was referenced Jul 30, 2026
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.
This is a maintainer replacement for #237. It keeps @hyknerf's SDK v1 compatibility rollback, rebases it over the #235 and #231 merges, and folds in the package-policy fixes from #227.
The branch removes the SDK v2 beta client/server packages, restores the SDK v1 client path, raises
@modelcontextprotocol/sdkto^1.30.0, keepszodas a direct runtime dependency, and preserves the server-manager close ownership fix already onmain.Credit:
zodas a direct runtime dependency and verified the packed manifest, but I did not reproduce the Docker install case, so Getting missing zod package when trying to install using Dockerfile #241 should stay open until the install path is confirmed after this lands.Validation:
npm test -- __tests__/package-manifest.test.ts __tests__/server-manager-legacy-handshake.test.ts __tests__/server-manager-close-ownership.test.ts __tests__/json-schema-validator.test.tsnpx tsc --noEmitCONFORMANCE_RESULTS_DIR=/tmp/pi-mcp-pr237-parent-conformance bash conformance/run.sh --scenario initializeCONFORMANCE_RESULTS_DIR=/tmp/pi-mcp-pr237-parent-conformance bash conformance/run.sh --scenario auth/2025-03-26-oauth-metadata-backcompatnpm pack --dry-run --json^1.30.0, no v2 beta client/server packages, directzod,ajv, andajv-formats