Generative UI

Putting an interface inside an agent conversation: a tool result or an agent's reply shown as controls a person can work in, where text would have been. Two things go by the name. A prebuilt web UI that an MCP tool points to and the host renders in a sandboxed iframe, which the MCP Apps extension specifies, is selected by the model and not generated by it; a user interface rendered from a stream of JSON objects the agent sends, which the A2UI specification describes, is. Generating an application's source at design time is generators.

Overview

SAP SHIPS

No core answer is documented.

Not covered: UI5 Web Components and UI Integration Cards render inside an MCP App as they do in any page, and the ui:// resource, the bridge to the host and the content security policy are the app author's, as UI5con_2026_MCPApps shows. The @ui5/webcomponents-ai package holds a Button, an Input, a PromptInput and a TextArea, and its documentation calls it experimental.

Unmapped because no artifact in the graph provides this behind the UI5 door: the samples demonstrate it and are nothing to depend on. SAP Joule is not assessed as a host; Marian Zeis wrote on 2026-07-13 that he could not verify documented Joule support for the MCP Apps extension.