modelcontextprotocol / modelcontextprotocol/ext-apps

Shared dependencies between UI instances

Open
#124 1 comment 0 reactions 1 assignee View on GitHub

@liady is already working on this.

Since Dec 10, 2025.

needs more work
Dominant language
TypeScript
Stars
2.9k
Forks
387
Avg merge
3h 21m
Merged PRs (30d)
6

Description

Context

An MCP App guest UI is self contained - and is required to include all of its dependencies (running in an isolated iframe). Use cases of MCP Apps will invlove multiple UI instances from the same server - and we might run into the question of "bloated" duplicate dependencies (i.e React, component libraries, etc).

This is not a new problem and is common in all microfrontend-based environements, however here we're looking at a lot of 3rd-party iframes that will have a 3rd-party host, so many of the existing solutions won't work.
We can imagine every host would need or try to solve it somehow at some point.

Not sure if this should be a part of the spec/recommendations (module federation? sharing resources between instances somehow?) - but opening here for a discussion.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.