Should agentic UI be controlled by the server or the host? 🤔 In mcp-ui, servers can now define the UI layout and effects, and hosts can render it with their own look and feel! Supports React and Web Components with Shopify's remote-dom. Hit us up with use cases (+Liad Yosef)

Check it out: The good-looking example uses the awesome @radix_ui. Can't wait to share the incredible apps and hosts that are working on mcp-ui support!

@Shopify @liadyosef lfg!!!

@Shopify @liadyosef @idosal1 love it. What's the latest on general interest to group this into the MCP spec? Is there anything I can do to help support from the Netlify side of things? Happy to help dig into any gaps

Great question. Currently, mcp-ui works on top of the existing spec, but we still need to tackle whether the UI protocol itself should be part of the spec (and if anything new is required). There's a similar question to other content types. It'd be amazing to have you in the CWG ( We're going to accelerate the process in the next few days!

@Shopify @liadyosef You guys are amazing

@Shopify @liadyosef looking very good @idosal1 ❤️

@Shopify @liadyosef @mattzcarey adding this to the agenda for tomorrow

@Shopify @liadyosef Should agentic UI be controlled by the server or the host? 🤔 Wouldn't this open up several security issues? One idea of server controlling this is the security side

@Shopify @liadyosef All JS from the server is executed in a completely sandboxed iframe. The host renders its components based on JSON messages between the host and iframe (courtesy of remote-dom).

@Shopify @liadyosef interesting move, especially for apps that need tight control over branding while keeping UI flexible. server-driven layouts can cut down dev cycles but watch out for latency spikes with complex effects

@Shopify @liadyosef That's exactly the use case. Please note that while the script comes from the server it's actually rendered locally inside a sandboxed iframe. There's no network latency