@modelcontextprotocol/server-legacy@2.0.0
MCP TypeScript SDK releases published @modelcontextprotocol/server-legacy@2.0.0. Minor Changes 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…
Why this signal matters
MCP TypeScript SDK releases published @modelcontextprotocol/server-legacy@2.0.0. This release-watch entry was generated from the project's official GitHub release feed and is kept separate from human-reviewed editorial analysis. Release notes: Minor Changes 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. Patch Changes 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 ! -…
Actionable summary
Treat @modelcontextprotocol/server-legacy@2.0.0 as an official release signal. Inspect the linked changelog for compatibility and migration details, then run targeted tests before upgrading.
- Agent usefulness
- 82/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- Review the official MCP TypeScript SDK releases release notes before upgrading.
- Check compatibility, migration, and security notes against your current agent stack.
- Run focused regression tests before production rollout.