MCP UI: Extending the frontier — Liad Yosef and Ido Salomon, MCP Apps

Transcript

[SPEAKER_01] OK. Hi, everyone. We built this talk, well, not really yesterday. We did this talk this morning, and it might already be out of date. I'm Amida Salaman. I'm the creator of MCPUI, co-creator of MCP Apps and maintainer, and also the creator of AngelCraft, if you were on the previous session. [SPEAKER_00] I'm Liad. [SPEAKER_00] I work with Ido on MCPUI. [SPEAKER_00] I co-created the MCP Apps spec with Ido. [SPEAKER_00] And I'm also co-founder of AeroLabs, which is a human agentic interfaces company. [SPEAKER_01] So MCP Apps are all around us. [SPEAKER_01] You might not even realize it, but the interactive applications you see today in ChatGPT, Claude, and others are actually based on MCP and the MCP Apps spec. But why do we need MCP Apps? And what's MCP Apps? You heard David this morning talk about it a little bit. [SPEAKER_00] We used to text. [SPEAKER_00] We used to MCP tools sending text to our chat agents. [SPEAKER_00] But that's not ideal, right? [SPEAKER_00] Because text is really bad. And actually, this was one of the main blockers of companies or tools not to send their data to ChatGPT, because they didn't want to be reduced to this thing, this wall of text, where you don't have identity. You don't know if this information came from Shopify, Booking, Expedia, or any other company. But what if every tool or every company could just send its own UI to the chat? So instead of us looking at this thing, we can just imagine that for the parts that are relevant, we can have the relevant UI. The relevant UI from Shopify, from Hugging Face, from Monday. And this can be not only presentation, this can be interactive. So we want to be able to respond to a user click on this Hugging Face widget. [SPEAKER_01] So we don't have to imagine it anymore. [SPEAKER_01] So back in May last year, I released MCPUI. [SPEAKER_01] The concept was pretty simple. [SPEAKER_01] There are a bunch of stuff around it. [SPEAKER_01] But the concept was pretty simple of how do we take UI and find some way to pass it over MCP. [SPEAKER_01] We need some general way to do that, so we can both have UI over MCP and have the communication between the UI and the host. [SPEAKER_01] Obviously, it also had community SDKs. [SPEAKER_01] And the general motivation was we don't need to throw away everything we know about UI and UX just to get into that new world of agents. [SPEAKER_01] We can simply adapt and use that and preserve our branding and identity and still be practical. [SPEAKER_01] And just a few months back, MCPUI, we partnered with Anthropik and OpenAI to really put this into the MCP standard as the first official extension called MCP apps. [SPEAKER_01] And as you can see here, it made a big splash. [SPEAKER_01] We had support from a bunch of hosts. [SPEAKER_01] Now VS Code and Cursor and Cloud and ChatGPT and Microsoft Copilot and a bunch of others already adopted it. [SPEAKER_01] And you have these really cool interfaces built in right to your assistants. And going back a little bit, there were early adopters for MCPUI. So these are some of the companies, shout out for HuggingFace, Sean, if you're here, that adopted MCPUI. [SPEAKER_00] So even a year ago, Shopify was already sending MCPUI chunks of all millions of stores of Shopify, online stores, send MCPUI chunks. [SPEAKER_00] HuggingFace, all of the HuggingFace spaces were MCPUI widgets. [SPEAKER_00] And now, once it's standardized, we have much bigger adoption. [SPEAKER_00] So we have VS Code, we have Cursor, we have Copilot, GitHub, ChatGPT are supporting MCPUI apps. [SPEAKER_00] Not only that, ChatGPT is recommending MCPUI apps as the way to build ChatGPT apps. [SPEAKER_00] So it's really standardized. [SPEAKER_00] Obviously, shout out to Postman and Goose and Cloud, the first one that released Cloud apps that actually supported MCPUI apps. [SPEAKER_00] But it's not just support from the big companies or the big hosts. [SPEAKER_00] We also have huge community adoption. [SPEAKER_00] We have people building plugins around MCPUI apps, building workshops around MCPUI apps, building all kinds of support around MCPUI apps. [SPEAKER_00] Pi just announced support in MCPUI apps, which is amazing. [SPEAKER_00] It's a terminal, right? [SPEAKER_00] But we have UI in the terminal right now. [SPEAKER_00] And we have all of these advocates that are speaking about MCPUI apps. [SPEAKER_00] There are even companies that are built around MCPUI apps to help other businesses build those apps. [SPEAKER_00] We have an official MCPUI apps repo with Entropic and OpenAI. [SPEAKER_00] There's amazing community engagement. [SPEAKER_00] We recommend for you to check it out. [SPEAKER_00] We have a work group, public work group meetings. [SPEAKER_00] And we're meeting tri-weekly, once every three weeks, just to push the standard forward because, as we can see, it's going to be the global standard for UI inside chat apps. [SPEAKER_00] And we're going to talk a little bit about the concepts behind MCPUI. Yeah. So let's talk about the core concepts. So the first and obvious one is how do we even pass UI over MCP? So in the old world of a few months back, when we wanted to do whatever, let's say we wanted to create the best playlist ever, we would type something into the chat and it would send out a tool call to our MCP server. So far, so good. What we would get back in response would be text. [SPEAKER_01] And as you know, text is suboptimal. [SPEAKER_01] But if we are using MCP apps, what we can do is instead return a resource. [SPEAKER_01] So you can return this actual HTML back to the host. [SPEAKER_01] The host supports MCP apps. [SPEAKER_01] So you can take that HTML and transform it into an interactive application. [SPEAKER_01] And when you say interactive, we mean interactive. [SPEAKER_01] So this is not just presentational. MCP apps also standardize the way that this UI can talk to the user and to its backend. Because just imagine if the user wants to favorite this song, then the suboptimal thing that would happen is that for this UI to speak to Spotify's backend and favorite this song. And then later when the user asks Claude, remind me which song I favorited, Claude wouldn't know because the UI spoke directly to the backend. [SPEAKER_01] The host supports MCP apps. [SPEAKER_01] So you can take that HTML and transform it into an interactive application. [SPEAKER_01] And when you say interactive, we mean interactive. [SPEAKER_01] So this is not just presentational. MCP apps also standardize the way that this UI can talk to the user and to its backend. Because just imagine if the user wants to favorite this song, then the suboptimal thing that would happen is that for this UI to speak to Spotify's backend and favorite this song. And then later when the user asks Claude, remind me which song I favorited, Claude wouldn't know because the UI spoke directly to the backend. But MCP app standardizes this message passing so that every UI chunk sends message back to the host. The host gets this message, in this case like a tool call. And the host decides what to do. In this case, it decides to actually call the server tool. But the control is in the hands of the host and everything stays in context. Okay, so seeing is believing. Let's see a quick example of what that looks like. [SPEAKER_01] So this is Claude, actual Claude. [SPEAKER_01] And let's say that I want to do something like analyze my funnel. [SPEAKER_01] So I type that in. In the old world, [SPEAKER_01] it would go out to, let's say, post-hog. [SPEAKER_01] And I will get this textual response, which is accurate, [SPEAKER_01] but it doesn't really help me understand what's going on. I have to read this whole thing now and try and see what's the deal. But with MCP apps, instead of doing this, I can just say, show me. And now, okay, the clicker is not yet up to par. But now what we'll have is this nice UI visualization actually created by post-hog. So they control the identity, the experience. It's actually their component that you would see in the website. And now I have a really cool way to just see the funnel in one glance. That's not all. The MCP apps isn't just UI generated by the server. There are also really cool innovations from Anthropic and other companies to do generative UI on top of MCP apps or even first-party UI in general. So for instance, this Claude feature says, let's say that I don't know what a funnel is, which is reasonable. I can ask what a funnel is and instead, again, getting that long textual answer. [SPEAKER_01] What would happen is that Claude would be able to generate this UI for me, [SPEAKER_01] explain exactly what I need or create some UI that I need to do some action [SPEAKER_01] and present it to me in a way that is very digestible. [SPEAKER_01] This is obviously applicable to a bunch of other stuff and you'll see it in other hosts as well. [SPEAKER_01] So let's look at another cool thing here is that this is not just presentational. [SPEAKER_01] As we said, it's interactive. [SPEAKER_01] So I can just click on it and it would give me a follow-up on the specific step of the funnel [SPEAKER_01] that I have a question about. [SPEAKER_01] So you can imagine how this goes into a bunch of other directions when you want to do interactive exploration. [SPEAKER_01] So how does it work in general? [SPEAKER_01] So let's go through the stages. [SPEAKER_01] We went to the host and we prompted something. [SPEAKER_01] We asked for funnel data. What happened is that it sent us a tool call to our MCP server. And again, instead of just returning text, that tool was actually pointing to a resource. That resource was our UI. So if you look at the code for it, it's super simple. You just register a resource and you just have it. So we return that resource back to the host. And the host, because it also supports MCP apps, can take that, transform it, put it. If you see, code-wise, if you want to build a host, it's just a React component that accepts that resource and also this callback, which is the way that we handle messaging between the UI and the host. So we take that and we render it inside a sandbox so it's secure. As we said, it's not presentational, so we also clicked on it. And once you click, what happens is that there is a bunch of events going back from the UI, from this view, all the way back to the model. So it can actually take out to do other tool calls or even follow up messages on your behalf or fetch additional resources, really completing this end-to-end bidirectional flow. So when we look at that, when we look at this flow, when we look at this architecture, [SPEAKER_00] it's not just technical change. [SPEAKER_00] It's not just the technology that's changing. [SPEAKER_00] It's also how we perceive the web. [SPEAKER_00] Because this is ushering a new web, a web where we don't need websites. [SPEAKER_00] We don't need all of those tabs just to organize an anniversary. [SPEAKER_00] We don't need to familiarize ourselves with a bunch of different UIs. [SPEAKER_00] We don't need to force ourselves to pass our intents to dashboards of companies [SPEAKER_00] where 90% of this UI is not relevant for an agent. [SPEAKER_00] If I have a personal assistant, I don't need most of it. [SPEAKER_00] I can just take this and I can decompose it to atoms and let my agent build them for me, right? [SPEAKER_00] Because I have my assistant that I can vary my intent to. [SPEAKER_00] So, for example, my agent, my proactive assistant can say, [SPEAKER_00] yeah, I see that you have an important university coming. [SPEAKER_00] And instead of Google just sending the data, Google can actually send a chunk of the Google Calendar. [SPEAKER_00] And now this is a win-win-win. [SPEAKER_00] Because for Google, it's amazing. [SPEAKER_00] It gets to keep its identity. [SPEAKER_00] For me, it's good because I know this interface. [SPEAKER_00] I recognize that it's Google. [SPEAKER_00] But it's good for the host as well. [SPEAKER_00] Because the host doesn't need to render that. [SPEAKER_00] We have domain experts. [SPEAKER_00] We have companies that spend decades perfecting user journeys. [SPEAKER_00] And we can't expect Claude or ChatGPT or any host to automatically generate all those UIs. [SPEAKER_00] And if I continue and I ask something for Amazon, [SPEAKER_00] so instead of Amazon just sending me the data of the product and thus reducing itself to be just a database, [SPEAKER_00] it can just send this chunk of Amazon. [SPEAKER_00] And I look at it and say, oh, it's Amazon. [SPEAKER_00] Okay, I know. [SPEAKER_00] And then I can complete the entire planning of my anniversary, the entire planning, in just one assistant chat. [SPEAKER_00] Right? [SPEAKER_00] And you can see that it pulled just the relevant parts of it. [SPEAKER_00] Because it pulled the venue from booking, but it knows me. [SPEAKER_00] It knows that I prefer something that's close to nature and not in the city. So it also knew to pull the map from booking. So instead of Amazon just sending me the data of the product and thus reducing itself to be just a database, it can just send this chunk of Amazon. And I look at it and say, oh, it's Amazon. Okay, I know. And then I can complete the entire planning of my anniversary, the entire planning, in just one assistant chat. Right? And you can see that it pulled just the relevant parts of it. Because it pulled the venue from booking, but it knows me. It knows that I prefer something that's close to nature and not in the city. So it also knew to pull the map from booking. That's because the assistant knew me. Booking doesn't know me that well. But booking knows how to book a venue. So this is real synergy between those. And we have to think about this new interaction mindset. Why? Because we have to remember that in this flow, the apps, the services, the tools, they no longer own my journey in the platform. Right? If I click something in booking, it doesn't go to Booking's backend. It goes to the host. So what we did with MCP apps is that every click, every interaction actually sends this kind of message back to the host. And this is breaking the model for all of the companies. So this is a new philosophy. But the messages can be put on a spectrum. So this spectrum represents how much control the UI wants for itself and how much control it gives to the host. So for example, notification, that's the highest level of control the UI has. It just notifies the host that something happened. For example, if I increase the number of items in my cart, it doesn't need to go to the host. It goes back to Shopify. But it just notifies the host that something happened. A tool call is the UI telling the host, call a tool. And prompt, that's the UI just releases all control and tells the host, just run this prompt and see what happens. So MCP apps really standardizes this new software flow. And that's something that we need to remember. Perhaps in two years, we won't have browsers as we know them. We won't have websites as we know them. We'll have a personal assistant that accepts only small chunks of UI. And this will replace our web journey. 2026 is going to be the year that we're going to standardize MCP apps as a global standard for UI. And yeah, but the spec is still evolving. There are a bunch of stuff happening. [SPEAKER_01] Just in those last, I think, two months, we shipped all of those, or almost all of those, based on community feedback, based on community work done by the work group, which you can join. So you're encouraged to do this. There is the official SDK, Xtaps. You can just use that to build your applications. It's very simple. There are built-in skills. So you just let your coding agent do it for you. You don't actually need to code anything. So you have this. And then it's important to remember that the reason to use this SDK is that it's always compliant with the spec. We always update both. So feel free to use it. You can see that just the issues and stuff that people open on it. So please feel free to do it. So what's next for MCP apps? Obviously, there are a bunch of stuff in the pipeline. But just to give you a taste, we have reusable views. The idea here is that today, for simplicity, whenever you render an app, we actually render a new one. So let's say that you're working with the same app multiple times. If you keep re-rendering it and you have some heavy applications, for example, Autodesk had this problem, it just takes a really long time and your experience will be bad. So we are working on ways to solve it. The first one is why can't we just reference that same view and push data into it? But the second one is actually to take this and flip the script. So another thing that we've been working on is interactions, not for the user to interact with the app and then the app sends it to the model, which we just saw. But what if we want the model to be able to interact with the view? We want Claude to be able to click on buttons or to fill forms or do anything inside the UI. So today we have solutions like WebMCP and things like that. We are working on a standardized way. So when the user interacts with the model, the app can actually expose tools for the model to interact with it, thus closing this loop. And you can check out the PR. It's still an open PR, but that's something that we work on in the community. And the most important thing is that MCP apps supports all the ways of generating UI because that's a question that we all get asked. What about generative UI? So if we put it on a spectrum, then we have the predefined UI. That's the classic MCP, Airbnb building its own UI, sending it to Claude or to chat GPT. That's predefined. That's a black box. That's good for 8% of the cases. But we have things that are a little bit more structured, like declarative UI. Like if you know JSON render or things like that, where the app can just declare the structure of the UI, but the components are being rendered by the host. So the host and the app are sharing the UI functionality and visibility. That's good for hosts that want to control the look and feel of the apps. For example, just imagine Claude probably doesn't want to have a booking UI, then an Airbnb UI, then an Expedia UI in the same chat flow, right? So this is pretty good middle ground. And on the other hand, you have the fully generative UI, which is what Claude, Anthropic released a few weeks ago, where the model just generates the UI out of thin air. Now, the nice thing is that MCP apps is really agnostic to how you generate the UI. MCP apps doesn't assume that Airbnb created the UI. Any part of this process can create the UI. And the feature that Claude released, which is the generative UI on the fly, actually uses MCP apps under the hood, right? So it's a generative UI that's being streamed into an MCP app. And then MCP apps closes that loop. So it's good for third party UI, which is a black box, but also first party UI. So that's something that we're working on standardizing. Now, the nice thing is that MCP apps is really agnostic to how you generate the UI. MCP apps doesn't assume that Airbnb created the UI. Any part of this process can create the UI. And the feature that Claude released, which is the generative UI on the fly, actually uses MCP apps under the hood, right? So it's a generative UI that's being streamed into an MCP app. And then MCP apps closes that loop. So it's good for third party UI, which is a black box, but also first party UI. So that's something that we're working on standardizing. We're doing a lot of work to do interoperability with other UI protocols like A2UI, which is the generative UI protocol by Google, or MCP, like we said. And we just want to build a unified standard for UI in chat apps. Yeah, and that's a cool summary about MCP apps. If you build an MCP app, it runs everywhere. LibreChat is an MCP app client. ChatGPT is a ChatGPT app client. But the same application works for, the same code base works for every host. Cool. So if you think about it, this isn't just some tech, right? This isn't some protocol. [SPEAKER_01] This is a new way to distribute applications. [SPEAKER_01] So if you look at just a few months back, Sam Altman said, I think it was October, that 800 million people are using ChatGPT on a weekly basis. [SPEAKER_01] That's 10% of the world's population. [SPEAKER_01] It's insane. [SPEAKER_01] The internet took 30 years to get to that number of users. [SPEAKER_01] And now it's not even 800 million, it's a billion. [SPEAKER_01] And it's not just ChatGPT, it's also Claude and VS Code. [SPEAKER_01] You have a potential audience that is at least 160 times the number of users that iPhone had when the app store launched. [SPEAKER_01] So how do you get started? [SPEAKER_01] There are two main ways. [SPEAKER_01] As a server, like if you're developing an app. [SPEAKER_01] So like I said, you go to Xapps repo, there's a QR code if you want to do it quickly. [SPEAKER_01] You have the skills, just use that. [SPEAKER_01] The other way is that if you're a host, so if you are building an application, an actual host application, you can just take MCPY's SDK, which is the recommended client SDK, it's also fully compliant with the spec. [SPEAKER_01] You just take that React component and you're done. [SPEAKER_01] It just supports apps out of the box. [SPEAKER_01] And you get hundreds of apps from Booking and other providers out of the box. [SPEAKER_01] So just to emphasize, there was a slide about skills. [SPEAKER_01] So it's really easy to create an MCP app. [SPEAKER_01] Just if you visit the site, we just pass through it, but it's just a skill. You just push it to cloud code and you generate an MCP app out of thin air. If you want to get involved in the spec itself, in how MCP apps are going to operate, if you want to help build the future of UI in agents, then obviously visit the official MCP apps repo. That's Xapps, open an issue, open a PR, participate in the discussion. We also have the official Discord for the MCP apps committee, where we do surveys and we interact with the community and with other hosts to decide on things that relate to MCP apps. And there's the community Discord, which is the coolest place to be because you have all of the users of MCP apps, be it people that build servers, companies that build hosts, that just talk to each other, share tips, troubleshooting, asking for features. That's the place to be if you're interested in MCP apps. So we said some scary stuff along the way, like the web is dying and all your websites aren't meaningless at this point. But I hope that you don't look at this as a threat, but more as an opportunity, a once in a 20 years opportunity to think about your apps again. I think what is the core user experience that we're looking to get? [SPEAKER_01] And imagine it not as a monolithic single app where people go to, but actually a part of a new web of applications, these chunks of UI that allow you to communicate between each other using a smart model in between. [SPEAKER_01] That's pretty insane. [SPEAKER_01] And with MCP apps, even this early in the ecosystem, this early in how agentic apps work, we already have standardization and they all work the same. [SPEAKER_01] Again, you can write your app once and it will run everywhere. [SPEAKER_01] So what does the future look like? [SPEAKER_01] We're not yet at Jarvis, but with MCP in general and MCP apps in particular, you can bring experiences that were impossible just a few months ago to every host in the world, including your own. [SPEAKER_01] So thank you. [SPEAKER_01] Thank you very much. [SPEAKER_01] Thank you very much. [SPEAKER_01] Thank you. We'll have a personal assistant that accepts only small chunks of UI. And this will replace our web journey. 2026 is going to be the year that we're going to standardize MCP apps as a global standard for UI. And... Yeah, but the spec is still evolving. I mean, there are a bunch of stuff happening. Just in those last, I think, two months, we shipped all of those, or almost all of those, based on community feedback, based on community work done by the work group, which you can join. So you're encouraged to do this. There is the official SDK, Xtaps. You can just use that to build your applications. It's very simple. There are built-in skills. So you just let your coding agent do it for you. You don't actually need to code anything, God forbid. So you have this. And then it's important to remember that the reason to use this SDK is that it's just always compliant with the spec. Like we always update both. So feel free to use it. You can see that just the issues and stuff that people open on it. So please feel free to do it. So what's next for MCP apps? Obviously, there are a bunch of stuff in the pipeline. But just to give you a taste, so we have reusable views. The idea here is that today, for simplicity, whenever you render an app, we actually render a new one. So let's say that you're working with the same app multiple times. If you keep re-rendering it and you have some heavy applications, so for example, Autodesk had this problem, it just takes a really long time and your experience will be bad. So we are working on ways to solve it. The first one is just why can't we just reference that same view and push data into it? But the second one is actually to take this and flip the script. So another thing that we've been working on is interactions, not for the user to interact with the app and then the app sends it to the model, which we just saw. But what if we want the model to be able to interact with the view? We want Claude to be able to click on buttons or to fill forms or do anything inside the UI. So today we have solutions like WebMCP and things like that. We are working on a standardized way. So when the user interacts with the model, the app can actually expose tools for the model to interact with it, thus closing this loop. And you can check out the PR. It's still an open PR, but that's something that we work on in the community. And the most important thing is that MCP apps supports all the ways of generating UI because that's a question that we all get asked. What about generative UI? So if we put it on a spectrum, then we have the predefined UI. That's like the classic MCP, Airbnb building its own UI, sending it to Claude or to chat GPT. That's predefined. That's a black box. That's good for 8% of the cases. But we have things that are a little bit more structured, like declarative UI. Like if you know JSON render or things like that, where the app can just declare the structure of the UI, but the components are being rendered by the host. So the host and the app are sharing the UI functionality and visibility. That's good for hosts that want to control the look and feel of the apps. For example, just imagine Claude probably doesn't want to have a booking UI, then an Airbnb UI, then an Expedia UI in the same chat flow, right? So this is pretty, pretty good middle ground. And in the other hand, you have the fully generative UI, which is what Claude, Anthropic released a few weeks ago, where the model just generates the UI out of thin air. Now, the nice thing is that MCP apps is really agnostic to how you generate the UI. MCP apps doesn't assume that Airbnb created the UI. Any part of this process can create the UI. And the feature that Claude released, which is the generative UI on the fly, actually uses MCP apps under the hood, right? So it's a generative UI that's being streamed into an MCP app. And then MCP apps closes that loop. So it's good for third party UI, which is a black box, but also first party UI. So that's something that we're working on standardizing. We're doing a lot of work to do interoperability with other UI protocols like A2UI, which is the generative UI protocol by Google, or MCP, like we said. And we just want to build a unified standard for UI in chat apps. Yeah, and that's a cool summary about MCP apps. If you build an MCP app, it runs everywhere. LibreChat is an MCP app client. ChatGPT is a ChatGPT app client. But the same application works for, the same code base works for every host. Cool. So if you think about it, this isn't just some tech, right? This isn't some protocol. This is a new way to distribute applications. So if you look at just a few months back, Sam Altman said, I think it was October, that 800 million people are using ChatGPT on a weekly basis. That's 10% of the world's population. It's insane. The internet took like 30 years to get to that number of users. And now it's not even 800 million, it's a billion. And it's not just ChatGPT, it's also cloud and VS Code. You have a potential audience that is at least 160 times the number of users that iPhone had when the app store launched. So how do you get started? There are two main ways. As a server, like if you're developing an app. So like I said, you go to Xapps repo, there's a QR code if you want to do it quickly. You have the skills, just use that. The other way is that if you're a host, so if you are building an application, an actually host application, you can just take MCPY's SDK, which is the recommended client SDK, it's also just fully compliant with the spec. You just take that React component and you're done. It just supports apps out of the box. And you get hundreds of apps from Booking and other providers out of the box. So just to emphasize, there was a slide about skills. So it's really easy to create an MCP app. Just if you visit the site, we just pass through it, but it's just a skill. You just push it to cloud code and you generate an MCP app out of thin air. If you want to get involved in the spec itself, in how MCP apps are going to operate, if you want to help build the future of UI in agents, then obviously visit the official MCP apps repo. That's Xapps, open an issue, open a PR, participate in the discussion. We also have the official Discord for the MCP apps committee, where we do surveys and we interact with the community and with other hosts to decide on things that relate to MCP apps. And there's the community Discord, which is I think the coolest place to be because you have all of the users of MCP apps, be it people that build servers, companies that build hosts, that just talk to each other, share tips, troubleshooting, asking for features. That's the place to be if you're interested in MCP apps. So we said some scary stuff along the way, like the web is dying and all your websites aren't meaningless at this point. But I kind of hope that you don't look at this as a threat, but more as an opportunity, like basically a once in a 20 years opportunity to think about your apps again. I think what is the core user experience that we're looking to get? And imagine it not as a monolithic single app where people go to, but actually a part of a new web of applications, these chunks of UI that allow you to communicate between each other using a smart model in between. That's pretty insane. And with MCP apps, even this early in the ecosystem, in this early in how agentic apps work, we already have standardization and they all work the same. Again, you can write your app once and it will run everywhere. So what does the future look like? We're not yet at Jarvis, but with MCP in general and MCP apps in particular, you can bring experiences that were impossible just a few months ago to every host in the world, including your own. So thank you. Thank you very much. Thank you very much. Thank you.