ProtocolsOfficial

MCP Apps 2.0 adopts split MCP TypeScript SDK packages while preserving wire compatibility

MCP Apps 2.0 moves to split MCP TypeScript SDK 2.0 client and server packages, Zod 4.2 and Node.js 20 while keeping 1.x and 2.x Views and hosts interoperable on the wire.

Why it matters

The release demonstrates that an interactive UI extension can evolve developer APIs without immediately breaking deployed hosts and views.

A closer look

Breaking changes affect dependencies, handler context, registration APIs and error types. A migration guide and cross-version tests accompany schema updates aligned with MCP 2.0 core types.

Who this is for

MCP Apps View, host and TypeScript service developers

Original sources

Revisions & corrections (1)

— Historical 90-day catch-up found the official 2.0 release absent from the catalog. Signed release notes, date, interoperability scope and caveats were read.

Related events

Protocols

A2UI separates model inference syntax from the wire protocol with Express and controlled decisions

On October 27, the Google A2UI team introduced swappable inference formats: a model can emit compact A2UI Express and let the SDK deterministically compile it against a component catalog into standard A2UI messages, while fixed-shape screens can use decision models to select predefined layouts.