Research / decision — evaluate A2UI vs MCP Apps for AttestoMCP's gate / connector UI inside agent hosts.
Context
- Google launched A2UI + MCP Apps (~week of 2026-06-23): https://developers.googleblog.com/a2ui-and-mcp-apps/ — "combines clarity with custom agents."
- A2UI is not supported inside Claude; MCP Apps is the current path for rendering UI in Claude.
- From the planning chat: the A2UI example runs as a standalone web app, not inside Claude or Gemini. A question was posted to the author on GitHub — no response yet.
Question to resolve
Can A2UI render AttestoMCP's consent/gate UI inside an agent host (Claude / Gemini), or do we stay on MCP Apps for the demo widget + the website's hosted "try-it-live" connector? This decides how those UIs are built.
Deliverable
A short write-up: A2UI vs MCP Apps for our case, the constraints (esp. Claude support), and a recommendation. Link the GitHub thread with the author.
Research / decision — evaluate A2UI vs MCP Apps for AttestoMCP's gate / connector UI inside agent hosts.
Context
Question to resolve
Can A2UI render AttestoMCP's consent/gate UI inside an agent host (Claude / Gemini), or do we stay on MCP Apps for the demo widget + the website's hosted "try-it-live" connector? This decides how those UIs are built.
Deliverable
A short write-up: A2UI vs MCP Apps for our case, the constraints (esp. Claude support), and a recommendation. Link the GitHub thread with the author.