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)

Robin Cartier perspective

This page is part of Robin Cartier's working AI knowledge graph: a practical research layer for production AI, recommendation systems, experimentation, GEO, and agentic web readiness.

The useful next step is to connect this concept back to applied product leadership and operating models.

Recommended next

Keep reading from this thread

From 500 indexed pages and articles.

  1. Wiki concept A2UI A framework-agnostic standard for declaring AI-generated UI intent so agents can drive client interfaces using the client's existing component catalog. Related by 115
  2. 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
  3. Wiki concept Agent-to-Agent Protocol Or A2A, is a protocol for remote agents to communicate with other agents or connect directly to frontends as part of distributed Related by a2ui