modelcontextprotocol / modelcontextprotocol/ext-apps
Feature parity with Apps SDK setWidgetState
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 387
- Avg merge
- 3h 21m
- Merged PRs (30d)
- 6
Description
I landed here coming from the ChatGPT apps and I was searching for an existing Issue or specification proposal that permits the me to persist a UI-Only widget state.
Useful both for rehydratation of the template and hiding information sensible to the user from the model and still display them in the UI (eg. bank account id)
It would be very useful to approach the problem as ChatGPT Apps SDK does:
- Persist a message level widget state mutable through the
setWidgetStateprimitive - Provide an hook (in mcp apps case a jsonrpc call) that let the template be aware on state change/rehydratation
- Distinguish
privateContentnot visible to the model but persisted into the state frommodelContent(link to apps sdk doc)
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 linked ChatGPT Apps SDK state-management documentation and the ext-apps protocol and SDK entry points. Define how message-level widget state, rehydration notifications, privateContent, and modelContent should interact, then document acceptance criteria covering persistence, UI visibility, and model visibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100