MCP UI lets servers return interactive application surfaces instead of plain tool results. But it raises a new question: what happens when the interface inside that surface is generated at runtime by the agent?
This talk shares lessons from building a Generative UI layer within MCP UI. MCP UI provides the app/resource boundary and host communication model, while frameworks like OpenUI provide the generated interface inside that boundary: a component registry, model-friendly UI language, streaming validation, form state, and explicit actions that route back to MCP tools.
The key shift is that MCP UI does not have to mean one fixed widget per tool result. A server can expose capabilities and context, the agent can generate the right interface for the task, and the host can still control rendering, permissions, actions, and observability.
The demo uses a data-dashboard workflow: an agent connects to a datasource, inspects data, generates an interactive dashboard with filters and drilldowns, then turns the result into persistent artifacts such as reports, documents, or slide decks.
___________________________
Presentation Language: English
Captioning will be available for attendees in 50+ languages through Wordly. See instructions in each room to utilize captioning.
