Google explores ways to combine A2UI and MCP Apps

Google has outlined three architecture patterns for combining A2UI and MCP Apps, aiming to give developers more flexibility when building agentic interfaces. The post explains how these approaches can balance native UI rendering, custom iframebased experiences, and support for existing app environments. The first pattern uses A2UI over MCP servers to render structured interfaces natively in the host application, avoiding iframe drawbacks while keeping MCP for tool and data access. The second pattern embeds MCP Apps inside A2UI components when developers need more complex, highly customized modules. The third pattern runs A2UI inside MCP Apps, letting legacy or nonA2UI environments support dynamic agentdriven interfaces through an embedded renderer. Google says the goal is to make it easier to choose the right setup based on security, performance, portability, and how much UI customization a project needs. The company also provided sample code, demo applications, and documentation links for developers who want to try the patterns in their own stacks.