feat(ui): migrate MCP Apps SDK to v2 - #3378
Merged
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The changes follow the documented v2 migration path and introduce no unresolved issues.
Review effort: Balanced
Findings: None
What changed in this PR
Migrates the MCP Apps UI to ext-apps v2 while preserving existing behavior and wire compatibility.
Changes:
- Upgrades ext-apps and adds required v2 peer dependencies.
- Moves
CallToolResulttype imports to the split client package. - Regenerates the npm lockfile.
| File | Description |
|---|---|
ui/src/hooks/useMcpApp.ts |
Updates the SDK type import. |
ui/src/lib/toolResult.ts |
Updates the tool-result type import. |
ui/package.json |
Declares ext-apps v2 dependencies. |
ui/package-lock.json |
Locks the migrated dependency graph. |
Files not reviewed (1)
- ui/package-lock.json: Generated file
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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
Migrate the MCP Apps UI from
@modelcontextprotocol/ext-apps1.7.5 to 2.0.3 and update its required SDK peers. The MCP Apps wire protocol and rendered behavior are unchanged.Why
Follow-up to #3370, which deferred the ext-apps 2.x migration because of its split SDK peers and TypeScript API changes. No separate issue is linked.
What changed
@modelcontextprotocol/ext-appsto^2.0.3; add required@modelcontextprotocol/client2.x andzod4.2+ peers.@modelcontextprotocol/sdk/types.jsCallToolResultimports with the SDK 2.x client package. ExistinguseAppinitialization and event handlers are compatible; no handler behavior changes are needed.Ptrcalls with Go 1.26's built-innew(expr), fixinggovetinline diagnostics without suppressing checks.@types/nodeunchanged. The SDK 2.x wire protocol is compatible with existing MCP Apps hosts.MCP impact
Prompts tested (tool changes only)
Security / limits
npm auditreports 0 vulnerabilities.Tool renaming
deprecated_tool_aliases.goNote: if you're renaming tools, you must add the tool aliases. For more information on how to do so, please refer to the official docs.
Lint & tests
./script/lint—GOTOOLCHAIN=go1.26.8 script/lintpassed (0 issues)../script/test—GOTOOLCHAIN=go1.26.8 script/testpassed. Also passedcd ui && npm ci,npm run typecheck,npm run build, andnpm audit(0 vulnerabilities). No separate browser/host smoke test was performed.Docs