Repository navigation
chore: bump ext-apps + example servers to 2.0.4 - #55
Merged
Merged
Conversation
Picks up WebMCP interoperability in the apps SDK (tools bridged to and from document.modelContext, on by default) and the pdf-server annotation validation fixes. Co-authored-by: ochafik <ochafik@anthropic.com>
2.1.0 was pulled from npm shortly after publishing; 2.0.4 is the current release line. Co-authored-by: ochafik <ochafik@anthropic.com>
ochafik
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps
@modelcontextprotocol/ext-appsand the 15 example app server packages (server-pdf,server-map, …) from ^2.0.0 to ^2.0.4.Changes picked up from the 2.0.1–2.0.4 line, notably 2.0.4: pdf-server defaults to a single
interactapp tool (per-action tools behind--split-app-tools), map-server gains aget-screenshotapp tool, the pdf viewer restores the saved page on tool-result re-delivery, and a dependency refresh clears the open npm audit findings (solid-js 1.9.17, sharp ^0.35.5).The branch briefly targeted 2.1.0, but that release was pulled from npm shortly after publishing — the second commit moves everything to 2.0.4, with the lockfile pinned there explicitly.
@modelcontextprotocol/node,@modelcontextprotocol/serverand the pinned SDK 1.29.0 are unchanged — they come from the SDK release line, not ext-apps. No code changes needed: the host only calls each package'screateServer(), whose signature stays compatible.Test plan
npm run build,npm run lint,npm test(91/91 pass) — all re-run at 2.0.4../scripts/test-e2e-internal.shpasses (OAuth flow, session management, tools/resources/prompts all served)./pdf/mcpinitialize + tools/list to confirm the mounted example apps serve from the new packages.registry.npmjs.org; all 16 packages resolve to exactly 2.0.4.Generated by Claude Code