modelcontextprotocol / modelcontextprotocol/ext-apps
Support for non-HTML-based surfaces
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 387
- Avg merge
- 3h 21m
- Merged PRs (30d)
- 6
Description
Is your feature request related to a problem? Please describe.
Many non-browser-based clients also interact with MCP, but by forcing all UI to text/html it is not possible for those clients to present reasonable experiences without being forced to introduce insecure and non-native experiences to their users.
Describe the solution you'd like
I would like to see support for either (a) fallback provisions or (b) a declarative model instead of explicit HTML/CSS/etc. or (c) both.
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
Start by reviewing the protocol's text/html UI surface and the constraints for non-browser clients. Compare the requested fallback provisions and declarative model, then define concrete scope and acceptance criteria with maintainers; no file or test is identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, html
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100