Topic

Agentic Web

All digests tagged Agentic Web

Rebuilding the web for agents — Liad Yosef, MCP Apps thumbnail

· 20:41

Rebuilding the web for agents — Liad Yosef, MCP Apps

The talk outlines the transition to the 'agentic web,' arguing that traditional websites and browser tabs are becoming obsolete as primary interfaces. The core shift involves breaking down complex UIs into atomic components that can be composed by personal AI assistants. The speaker, a co-creator of the MCP Apps specification, details how MCP Apps allows servers to hand real UI interfaces back into a chat context, solving the 'last mile of interaction.' Furthermore, the talk introduces the need for a standardized discovery layer, proposing the use of `AI catalog.json` to make websites 'agent ready' and accessible to autonomous agents.

Key takeaways

  1. MCP Apps Solves Last-Mile Interaction 1:42

    MCP Apps allows providers to send UI chunks into chats, ensuring that services retain their brand identity and functionality rather than being reduced to text or databases. This solves the 'last mile' problem for agents, enabling complex interactions like booking hotels or viewing 3D models within a unified chat context.

  2. The Agentic Web Paradigm Shift 5:40

    The web is shifting from being a collection of siloed websites (requiring multiple tabs and different UIs for the same intent) to being composed by personal assistants. Assistants become the primary entry point, making websites themselves less critical for task completion.

  3. Need for Agent-Specific Discovery 19:16

    Traditional standards like `llms.txt` are insufficient because agents often ignore them, preferring to navigate to docs or homepages. The solution requires a standardized, machine-readable directory, such as the proposed `AI catalog.json`, to expose a website's MCP and API servers directly to agents.

Watch on YouTube Full article

MCP Apps: Extending the Frontier — Ido Salomon & Liad Yosef thumbnail

· 18:38

MCP Apps: Extending the Frontier — Ido Salomon & Liad Yosef

MCP Apps introduces a standardized protocol for embedding rich, interactive user interfaces directly into AI chat assistants, moving beyond text-only responses. This system allows services (like Shopify or PostHog) to maintain their brand identity and full UX within the agentic loop. By standardizing how tool calls link to rendered web components, MCP Apps ensures that interactions flow back through the host, giving the host control over the user journey. The goal is to enable a 'write once, run anywhere' model for applications across major AI platforms (ChatGPT, Claude, etc.), fundamentally changing how the web is consumed in the era of personal assistants.

Key takeaways

  1. The Problem with Text-Only Chat 0:24

    Textual responses are suboptimal for conveying complex information or maintaining brand identity. Companies want their full UX to be visible and interactive within the chat interface, rather than being reduced to a textual database.

  2. MCP Apps Protocol 1:46

    MCP Apps is an open protocol that allows services to send their UI directly into the chat. This enables not only visualization but also full interactivity, allowing users to act on the displayed content (e.g., favoriting a song).

  3. Interactive Flow Control 3:30

    When a user interacts with an embedded app component (like clicking a button), MCP Apps standardizes this flow by sending a message back to the host, which maintains control and decides whether to execute a tool call on behalf of the user.

  4. The Agentic Web Vision 10:53

    MCP Apps envisions a future where services are broken down into 'atoms' of UI that can be composed by personal assistants, allowing users to complete complex tasks without leaving the chat environment.

Watch on YouTube Full article