modelcontextprotocol/typescript-sdk @modelcontextprotocol/server-legacy@2.0.0 on GitHub

#2477 8e1d2e9 Thanks @felixweinberger! - Move the schema source modules (spec schemas, OAuth schemas, protocol constants) into @modelcontextprotocol/core and resolve them from there as a regular runtime dependency instead of bundling a private copy into each package. An application importing more than one of the packages now evaluates a single shared schema graph with shared object identity. @modelcontextprotocol/core gains a ./internal subpath (SDK-internal contract; may change in any release) and the four packages now version together.

#2402 a400259 Thanks @felixweinberger! - First beta release of SDK v2 with support for the MCP 2026-07-28 specification
revision. See the migration guides for upgrading from v1
(docs/migration/upgrade-to-v2.md) and adopting the 2026-07-28 revision
(docs/migration/support-2026-07-28.md).
#2405 f172626 Thanks @mattzcarey! - Ship CommonJS builds alongside ESM. Each package now emits both .mjs/.d.mts
and .cjs/.d.cts (via tsdown format: ['esm', 'cjs']), and its exports map
adds a require condition so require('@modelcontextprotocol/…') works from
CommonJS consumers. Output extensions are normalized across all packages
(@modelcontextprotocol/core moves from .js/.d.ts to .mjs/.d.mts); the
public import paths are unchanged.
#2476 e0a0ab7 Thanks @felixweinberger! - Build protocol-revision wire schemas lazily on first validation instead of at import. Each revision's schema set is now constructed by a module-level memoized factory, so importing the client or server package no longer pays the construction cost of both frozen wire-schema graphs up front. Method membership in the revision registries stays static, the schemas themselves are unchanged, and registry lookups keep returning reference-identical schema objects.
Updated dependencies [a400259, 44797d7, f172626, 8e1d2e9, f413763]:
- @modelcontextprotocol/core@2.0.0