modelcontextprotocol / modelcontextprotocol/ext-apps
Mechanism to defer `UIResource` rendering for intermediate tool calls
@idosal is already working on this.
Since Jan 29, 2026.
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 387
- Avg merge
- 3h 21m
- Merged PRs (30d)
- 6
Description
Summary
The current specification does not clearly define the expected Host behavior when a model executes multiple tool calls, each returning a UIResource.
Questions
-
Rendering multiple UIResources: If the model runs N tool calls, each with an associated UIResource, should the Host render N iframes? Or is it up to the Host to decide how and when to display these UIs?
-
Priority field behavior: The MCP spec includes a
priorityannotation (0.0 to 1.0), but it's unclear:- What is the expected behavior when
priorityis not set? - What should Hosts do when all UIResources have the same priority (e.g., all
1.0)? - How does
priorityapply to UI rendering decisions specifically?
- What is the expected behavior when
Understanding the intended behavior would help ensure consistent UX across different Host implementations.
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.
Assessment
This issue has not been assessed yet.