Version Packages (beta)

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@modelcontextprotocol/client@2.0.0-beta.1

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).

@modelcontextprotocol/codemod@2.0.0-beta.1

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).

@modelcontextprotocol/core@2.0.0-beta.1

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).

@modelcontextprotocol/express@2.0.0-beta.1

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).
• Updated dependencies [a400259]:
  • @modelcontextprotocol/server@2.0.0-beta.1

@modelcontextprotocol/fastify@2.0.0-beta.1

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).
• Updated dependencies [a400259]:
  • @modelcontextprotocol/server@2.0.0-beta.1

@modelcontextprotocol/hono@2.0.0-beta.1

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).
• Updated dependencies [a400259]:
  • @modelcontextprotocol/server@2.0.0-beta.1

@modelcontextprotocol/node@2.0.0-beta.1

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).
• Updated dependencies [a400259]:
  • @modelcontextprotocol/server@2.0.0-beta.1

@modelcontextprotocol/server@2.0.0-beta.1

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).

@modelcontextprotocol/server-legacy@2.0.0-beta.1

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).

[pkg-pr-new]

Open in StackBlitz

@modelcontextprotocol/client

npm i https://pkg.pr.new/@modelcontextprotocol/client@2404

@modelcontextprotocol/codemod

npm i https://pkg.pr.new/@modelcontextprotocol/codemod@2404

@modelcontextprotocol/core

npm i https://pkg.pr.new/@modelcontextprotocol/core@2404

@modelcontextprotocol/server

npm i https://pkg.pr.new/@modelcontextprotocol/server@2404

@modelcontextprotocol/server-legacy

npm i https://pkg.pr.new/@modelcontextprotocol/server-legacy@2404

@modelcontextprotocol/express

npm i https://pkg.pr.new/@modelcontextprotocol/express@2404

@modelcontextprotocol/fastify

npm i https://pkg.pr.new/@modelcontextprotocol/fastify@2404

@modelcontextprotocol/hono

npm i https://pkg.pr.new/@modelcontextprotocol/hono@2404

@modelcontextprotocol/node

npm i https://pkg.pr.new/@modelcontextprotocol/node@2404

commit: 6008533

[claude]

LGTM — auto-generated changesets release PR (beta.0 → beta.1 version bumps and changelog entries); merge whenever the team is ready to publish the beta.

Extended reasoning...

Overview

This is the standard Version Packages (beta) PR opened by the changesets/action bot. It bumps every publishable package from 2.0.0-beta.0 to 2.0.0-beta.1, prepends the corresponding CHANGELOG entries (all pointing at the consolidated #2402 beta-release changeset), and records the consumed beta-release changeset in .changeset/pre.json (plus a whitespace reformat of that file). No source code, build configuration, or workflow files are touched.

Security risks

None. The diff contains only version strings, generated changelog prose, and changesets bookkeeping. There are no dependency changes, no auth/crypto/permission code, and no executable logic.

Level of scrutiny

Low for code review purposes — the content is deterministically generated by the changesets tooling from the beta-release changeset merged in #2402, and the version/dependency bumps are internally consistent (middleware packages reference @modelcontextprotocol/server@2.0.0-beta.1). The only meaningful decision attached to this PR is when to merge it, since merging triggers the npm publish — that release-timing call stays with the maintainers and is not a code-correctness question.

Other factors

The bug-hunting system found no issues, and there are no outstanding reviewer comments on the PR. The CHANGELOG skipping a 2.0.0-beta.1-only entry (no beta.0 section) is an artifact of the earlier alpha-changeset pruning (#2403) and the pre-mode bookkeeping, not something introduced or fixable in this generated PR.