modelcontextprotocol / modelcontextprotocol/ext-apps
Potential interoperability with A2UI
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 387
- Avg merge
- 3h 21m
- Merged PRs (30d)
- 6
Description
Exploring potential interoperability directions with A2UI.
Two directions -
- MCP Apps content being rendered as a "black box" A2UI leaf component, or -
- Abstract "A2UI" content returned from an MCP Apps server (instead of an HTML).
Both ways make sense, and the two methods (MCP-driven vs Agent driven) can be complementing this way.
There's a constant tension between the hosts' needs for UI control and streamlining, and the servers' needs for branding and customized UI. Each method puts emphasis on a different end of this scale.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the linked A2UI material and comparing the two proposed directions—an A2UI leaf component for MCP Apps content or A2UI content returned by an MCP Apps server; a concrete direction and completion criteria are still needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ai, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100