From 6ae7eb2bfb62b8c7895d7d74bf485b24b558f2a3 Mon Sep 17 00:00:00 2001 From: unknown Date: Fri, 23 Oct 2026 21:10:20 +0530 Subject: [PATCH] docs: say which ext-apps line to use with the v1 SDK ext-apps 1.x peers on @modelcontextprotocol/sdk ^1.29.0 while 2.x peers on the split v2 packages. The README only shows the v2 install, so a project still on the v1 SDK has no pointer to the 1.x line. --- README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README.md b/README.md index ab4004d66..3bccb7681 100644 --- a/README.md +++ b/README.md @@ -145,6 +145,15 @@ npm install -S @modelcontextprotocol/ext-apps \ zod@^4.2.0 ``` +Still on the v1 SDK (`@modelcontextprotocol/sdk` 1.x)? Stay on `ext-apps` 1.x, +which peers on `@modelcontextprotocol/sdk@^1.29.0`; 2.x peers on the v2 +packages above instead, so `npm install @modelcontextprotocol/ext-apps` on its +own pulls in a second SDK next to yours: + +```bash +npm install -S @modelcontextprotocol/ext-apps@^1 @modelcontextprotocol/sdk@^1.29.0 +``` + The wire protocol is unchanged between `ext-apps` 1.x and 2.x: a 2.x View works in a 1.x host and a 2.x host renders 1.x Views. See the [migration guide](https://apps.extensions.modelcontextprotocol.io/api/documents/migrate-to-v2.html)