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: @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
Details
Coverage
For your agent
- Ref
capability:generative-ui- JSON
- /capabilities/generative-ui.json
- MCP
- Connecting an agent