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: @cap-js/agents 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 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.

SourceCAP-level Agents — capirechecked
THE COMMUNITY ADDS

A plugin can swap in its own protocol adapter for @cap-js/mcp, which is how cap-mcp-apps shows query results as a @ui5/webcomponents table with buttons for annotated unbound actions.

Artifacts1

1 of 1 artifacts
ArtifactSignals
CDS plugins1
cap-mcp-appsShows @cap-js/mcp query results as a table inside the agent host
Signals
none

Content1

Group by
Piece, what it offers
SAP’s compositional design system: Craft enterprise UIs with AI on the fly
SAP TechEd — session catalogue, TalkThe reasoning

Details

Coverage
statecommunity only, CAP
assessed
also inUI5
SourceCAP-level Agents — capirechecked SourceCAP-level Agents, More to come — capirechecked SourceModel Context Protocol Adapter — capirechecked Sourcecap-mcp-apps — READMEchecked
For your agent
Ref
capability:generative-ui
JSON
/capabilities/generative-ui.json
MCP
Connecting an agent