modelcontextprotocol / modelcontextprotocol/ext-apps
Clarify MCP Apps behavior with code mode
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 387
- Avg merge
- 3h 21m
- Merged PRs (30d)
- 6
Description
MCP Apps doesn't directly address either host-side or server-side code mode.
This leaves room for different interpretations of how UI tools should be exposed and fetched in these scenarios.
Host-side -
Should the Apps spec define how hosts should fetch views when the UI tools are discovered dynamically?
Server-side -
Should the Apps spec define how hosts should expose UI tools? For example, should UI tools always be exposed outside the code-mode paradigm to match naive 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.
Research direction
No file, test, or entry point is named. Start by reviewing the MCP Apps specification's handling of UI tools and the host-side and server-side code-mode scenarios described here. Done means the specification clearly defines how UI views and tools are discovered and exposed in both scenarios.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100