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 generatorsGeneratorsGetting from nothing to a project that runs, and from a project that runs to one that has the piece you just decided you need. Two different moments: the first is a one-time decision about layout, the second recurs for the life of the project.SAP and community, narrow by design.
Overview
No core answer is documented.
Not covered: UI5 Web Components@ui5/webcomponentsSAP's UI elements as standard custom elements, ui5-button among them, implementing SAP Fiori design and usable from plain HTML, React, Angular or Vue.sap official, ui5 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_MCPAppsUI5con_2026_MCPAppsFive runnable MCP servers whose tools return a prebuilt UI beside their text result, from plain HTML through UI5 Web Components and UI Integration Cards to a UI5 linter workflow and an ARC-1 transport review.independent, ui5 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 JouleSAP JouleSAP's unified AI engagement layer across SAP applications: Joule Work is where a user expresses intent, Joule Assistants coordinate agents across business functions, and Joule Agents carry out the tasks, provisioned on BTP as a formation against SAP Cloud Identity Services.sap official, btp is not assessed as a host; Marian ZeisMarian Zeismaintains 35 entries, created 25 pieces, contributed to 86 entries wrote on 2026-07-13 that he could not verify documented Joule support for the MCP Apps extension.
No artifact is documented here yet.
No core answer is documented.
Not covered: @cap-js/agents@cap-js/agentsSAP's own CDS plugin for building agents inside a CAP service, wired to audit logging and telemetry through peer dependencies rather than leaving observability to the author.sap official, cap serves a chat preview for local development, which capire calls rudimentary and experimental, and returning structured data over A2A, Data Parts, is on capire's list of features still to come. The describe, query and call tools of @cap-js/mcp@cap-js/mcpA CAP plugin that serves an @mcp-annotated service over MCP with three generated tools, describe, query and call_action, and writes its endpoint into the local agent's configuration in development.sap official, cap are documented with no ui:// resource.
The second sentence rests on an absence: the adapter's guide lists the three tools and a server card and mentions no UI resource.
No artifact is documented here yet.
Artifacts
Nothing is mapped here yet.
Content
Seen working
Neither the package manifest nor the repository tree declares a licence.
Details
Coverage
For your agent
- Ref
capability:generative-ui- JSON
- /capabilities/generative-ui.json
- MCP
- Connecting an agent