ChangeGamer

A2UI: Google's Declarative Agent-to-UI Protocol (vs AG-UI, MCP Apps)

Guide references · updated · 1,115 words · ~5 min read · 6 cited sources · Markdown variant

What A2UI is: the open, Apache-2.0 standard in which agents send declarative JSON describing the intent of a UI and the client renders it from a catalog it controls; the four v0.9 message types, transport requirements, renderer status, and how A2UI relates to AG-UI, A2A and MCP Apps.


A2UI is an open standard in which an agent sends declarative JSON that describes the intent of a user interface, and the client renders that description using a catalog of components the client itself controls. The agent describes; the client decides what actually gets drawn.

Key facts

What is A2UI?

A2UI is a protocol for the payload an agent sends when it wants the user to see or fill in something richer than text. Instead of returning HTML or executable code, the agent returns declarative JSON that states the intent of the interface. The client maps that description onto a catalog of components that the client controls. The source is the project README at https://raw.githubusercontent.com/google/A2UI/main/README.md and the repository at github.com/google/A2UI.

Version status, as stated by the README at the time of writing: v0.9.1 is the production release (a patch of the stable v0.9 family) and the v1.0 spec is a release candidate. Treat v1.0 as not yet final until the README says otherwise. The README also labels the project an early-stage public preview and says to expect changes. The license is Apache 2.0.

Provenance and launch: the Google Developers Blog post "Introducing A2UI: An open project for agent-driven interfaces" (author shown as Google A2UI Team) is dated December 15, 2025 and calls that day "the first public milestone of A2UI", at format version v0.8. The blog describes A2UI as complementary to other agentic UI frameworks, not as a replacement for them. a2ui.org states it was created by Google with contributions from CopilotKit and the open-source community, with a "Copyright Google 2025" footer; its pages list v1.0 as a candidate, v0.9.1 as current and v0.8 as legacy. Note: the blog links github.com/google/A2UI, while a2ui.org and the README quickstart clone github.com/a2ui-project/a2ui; no fetched source says which is canonical or that the repo moved.

How do A2UI messages work?

The v0.9 specification (https://raw.githubusercontent.com/google/A2UI/main/specification/v0_9/docs/a2ui_protocol.md) defines four message types. Each message contains exactly one of these keys:

createSurface carries these fields: surfaceId (required, globally unique), catalogId (required), theme (optional) and sendDataModel (optional boolean).

Per the spec, a catalog ID need not resolve to a deployed resource; the client and the server must agree on well-known IDs. The catalog is therefore a shared agreement about which components exist, not something fetched at runtime.

What transport does A2UI need?

The spec places three requirements on the transport: reliable, ordered delivery; message framing; and metadata support, a way to associate metadata with messages (needed for sendDataModel and action context). Named examples of framing are JSONL, WebSocket frames or SSE events. A bidirectional return channel is optional. A2UI does not define the transport itself, which is why the README describes it as compatible with A2A and AG-UI and why A2UI rendering can run over AG-UI. Do not conflate the layers: A2UI is the UI-description payload; AG-UI and A2A are the protocols that carry it. For the layering of agent-to-agent and agent-to-tool protocols see /resources/mcp-vs-a2a.

Which renderers exist?

Per the renderers reference (https://raw.githubusercontent.com/google/A2UI/main/docs/public/reference/renderers.md):

"Planned" means planned in the project's own documentation, not shipped.

A2UI vs AG-UI vs MCP Apps: which should you use?

These do not occupy the same layer, so the decision is mostly about which problem you have.

This entry does not claim a head-to-head ranking, adoption comparison or compatibility between A2UI and MCP Apps or WebMCP; the sources above do not state one.

Security note (stated vs inferred)

Stated by the sources: the Google Developers Blog post says "A2UI is a declarative data format, not executable code" and that clients keep a catalog of trusted, pre-approved components that agents can only request from; a2ui.org says the same about the catalog. Neither source claims a formal security audit or guarantee.

Inference, not a statement from the sources: declarative data of this kind is easier to validate than executable output, but whether your renderer is actually safe is a property you must confirm yourself, not a guarantee. Keep treating agent output as untrusted input; see /resources/agentic-security-checklist.

See also: /resources/generative-ui-for-agents, /resources/mcp-apps-explained, /resources/mcp-vs-a2a, /resources/webmcp, /resources/agent-client-protocol (editor/client to coding-agent layer; JSON-RPC, reuses MCP JSON representations where possible)

Verified sources

#a2ui #generative-ui #ag-ui #a2a #mcp-apps #protocols #frontend #agents

Category: Guide references

Free to read, always. Want this whole reference corpus inside your own agents? A €5 starter key unlocks every premium reference for one agent; the €25 corpus license licenses the full corpus as RAG / fine-tuning data with an AI-use grant (procurement one-pager: /corpus-license); the €150 enterprise license adds redistribution rights.

Machine formats: Markdown · JSON · offers at /api/pricing.json · payment at /api/payment.json. Preview the exact corpus format free as NDJSON.