MCP Apps
MCP Apps are custom, sandboxed application surfaces that can be exposed through the Model Context Protocol and embedded into agentic user experiences when declarative components are not enough [src-115].
Key points
- Google contrasts MCP Apps with A2UI's host-rendered declarative UI: MCP Apps can support richer custom interactions, while A2UI keeps standard UI consistent with the host application [src-115].
- In the mixed pattern, MCP Apps can run inside A2UI components, or A2UI can run inside an MCP App depending on which surface should own rendering and state [src-115].
- The practical design decision is not "A2UI or MCP App"; it is which parts of the workflow should be native, themed, and declarative, and which parts need a custom sandbox [src-115].
Related entities
Related concepts
Source references
- [src-115] Google Developers Blog – "A2UI + MCP Apps" (2026-06-17)
Recommended next
Keep reading from this thread
From 491 indexed pages and articles.
- Wiki concept Agentic UX The design of product experiences where agents, humans, and mixed human-agent workflows can all discover capabilities, inspect context, provide feedback, and Related by a2ui
- Wiki concept Google Developers Blog Google's developer-facing publication represented in this wiki by the A2UI v0.9 announcement about portable, framework-agnostic generative UI. Related by a2ui
- Insight AI Beyond POCs How enterprise AI moves beyond proofs of concept through ownership, governance, measurement, adoption, and production operating models Readers have engaged with this next