@modelcontextprotocol/server-legacy@2.3.0
MCP TypeScript SDK releases published @modelcontextprotocol/server-legacy@2.3.0. Patch Changes - 2908 (https://github.com/modelcontextprotocol/typescript-sdk/pull/2908) 633dd3e (https://github.com/modelcontextprotocol/typescript-sdk/commit/633dd3e12bff6869c932c4a526341622320912b1) Thanks @claude (https://github.com/apps/claude)! - The license field of the…
Why this signal matters
MCP TypeScript SDK releases published @modelcontextprotocol/server-legacy@2.3.0. This automated release-watch entry was generated from the project's official GitHub release feed and is kept separate from human-reviewed editorial analysis. Release notes: Patch Changes - 2908 (https://github.com/modelcontextprotocol/typescript-sdk/pull/2908) 633dd3e (https://github.com/modelcontextprotocol/typescript-sdk/commit/633dd3e12bff6869c932c4a526341622320912b1) Thanks @claude (https://github.com/apps/claude)! - The license field of the package manifests is now Apache-2.0 ; the LICENSE file shipped in each package carries the full terms, including the MIT text for earlier contributions. No code change. - Updated dependencies 633dd3e (https://github.com/modelcontextprotocol/typescript-sdk/commit/633dd3e12bff6869c932c4a526341622320912b1) : - @modelcontextprotocol/core@2.3.0
Actionable summary
Treat @modelcontextprotocol/server-legacy@2.3.0 as an official release signal. Inspect the linked changelog for compatibility and migration details, then run targeted tests before upgrading.
- Agent usefulness
- 77/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.