Chat and coding assistants still hand you walls of text when a button, a chart, or a small interactive view would say it faster. Liad Yosef, who co created MCP UI, walks through MCP Apps: a way for an MCP server to return a real interactive interface instead of a block of text, built on the MCP UI project he started and now shaped through an open working group in the MCP committee. A tool call links to a registered resource, the host renders it as a web component, and clicks flow back into the agentic loop, so the same funnel that would take a paragraph to explain becomes something you can see and act on at a glance. The payoff is write once, run anywhere. Because it is a standard rather than a bespoke integration, a UI a server ships shows up across every host that supports it, and Yosef points to adoption by hosts and tools already in the ecosystem. He is candid that the spec is still evolving, with live work on how the app and the chat talk to each other and how apps interoperate, and an open invitation to contribute. The bigger bet is distribution: when a host reaches hundreds of millions of weekly users, a server that speaks MCP Apps reaches all of them at once. Speaker info: Liad Yosef - https://x.com/liadyosef - https://linkedin.com/in/liadyosef - https://ora.ai Ido Salomon - https://x.com/idosal1 - https://www.linkedin.com/in/ido-salomon/ Timestamps: 0:00 - Why we need MCP Apps 1:52 - From walls of text to interactive views 2:29 - MCP UI, created and adopted 4:26 - An open working group in the MCP committee 5:04 - How a tool call becomes an interface 6:31 - Standardizing the flow 8:52 - The architecture: resources and web components 10:10 - Consuming apps through the browser 14:29 - What's still evolving in the spec 16:07 - Interoperability across hosts 17:14 - Write once, reach hundreds of millions