UI renderers
How a UI plugin's interface reaches a host that is not Datalayer's own page, one spec each
under agentspecs/ui-renderers/. A renderer is not an interface: a UI plugin
says the renderers it may be exposed through, and an application names, per UI plugin, the
one it uses. A renderer that is not enabled is listed, and an application that is offered
cannot use it yet.
| Renderer | Id | Enabled | The UI plugins it can carry |
|---|---|---|---|
| A2UI | a2ui | yes | a2ui-surface, a2ui-view, app-components, app-elements, app-page |
| MCP Apps | mcp-apps | no | app-page |
| MCP UI | mcp-ui | no | pap-sign-in |
Each renderer
A2UI (a2ui)
An agent describes an interface — a form, a table, a card — as a tree of components from a catalogue the host allows, and the host renders it; what the user does in it comes back to the agent as an action.
MCP Apps (mcp-apps)
An MCP server ships an interactive app with a tool: the host renders it in a sandboxed frame beside the conversation, and the app calls the server's tools through the host.
MCP UI (mcp-ui)
An MCP tool answers with a UI resource — HTML, a remote page or a component — that the host renders in place of plain text.