WebMCP

Speaker 0: We do have Austin. I was wondering where you got Alright. Hey. How many of y'all have heard of WebMCP? Raise of hands. Speaker 0: Okay. Quite a few of you. Awesome. So So it just hit Chrome 1 46. I work for the w 3 c. Speaker 0: I'm standardizing it. And there's a lot of misconceptions about it. First of all, it's not MCP. It's probably the most common misconception we get. What? Speaker 0: And I don't know why you could click that. Right? It's not like it's in a name or anything. So, no. So WebMCP is a web standard or an upcoming, potentially, you know, in the process of being a web standard for tool calling on in client JavaScript on web pages, meaning that you expose tools Can I use this 1? Speaker 0: I'll just have a little closer here. Sure. You expose tools in your client JavaScript, and the agents, browser agents, OpenClaw, whoever that supports WebMCP could just see it as a tool as, like, a JSON schema in its context or, you know, code, if it's code code, whatever. But yeah. So we have it here. Speaker 0: This is what it looks like. You have your WebMCP JS. You have your integrated browser agent or you have an in page agent, things like this. And, I just wanna show some cool stuff you can do with it today. You know, it started adding to your website. Speaker 0: I maintain some polyfills. So this is my Carsten, form of Chromium where I've been working on the streaming, tool call version of WebMCP. So anyone have any idea what they want to, Vibe code or, like, for a website? Vibe code pong. Can you write me a quick pong, please? Speaker 0: Actually, it doesn't do. It's just CSS and HTML. I want a hotdog that gets bigger every time I click it. Oh, it's also JavaScript. It's gonna alright. Speaker 0: What's that? Make Wikipedia. Alright. Speaker 1: Make make make Wikipedia. Speaker 0: Just once. Don't call the tool multiple times. I did not add protections there. Alright. So it's gonna stream, the arguments from JavaScript here. Speaker 0: It's calling the model sort of thing, and it's just going to dump these into the page. So you can see tool calls are coming in, and it's a streaming tool call that's also something that SAP doesn't have. So right now it's writing with CSS, and then we'll start inputting the JavaScript into the page. So there you go. You get a bot coding Wow. Speaker 0: Round of applause. Awesome. And so this is happening all client side. There's no server involved. This is a Chrome extension, The Chrome team put together for WebMCP. Speaker 0: Oh, it it listened to me. It's making another website. Okay. So, yeah, this is fun stuff we can do. You know, this is, you know, web is the web standard. Speaker 0: If you have a website and, you know, you just wanna treat the browser as, like, an intelligence layer you can build on, you don't need to ship your own custom agent. You can just assume that it'll be there. Oh, there we go. No way. That's that's pure CSS. Speaker 0: I have it, so I can't run JavaScript. So that's fine. Okay. So alright. There's a couple other things. Speaker 0: We've also got work with the folks from, Anthropic on doing, like, Webexip and NTPF. So how many do you guys know NTPFs or MTP UI? So you can just run because it's just an iframe. You can run WebMCP tools inside of there. So this is a game of tic tac toe, and the agent will render it, and I can play it with it here. Speaker 0: If you guys wanna pull this up, it's MTP UI, m t p u I .mtpe.i. It's a horrible domain. But, sorry. So, anyway, we can start here. Where's your QR code? Speaker 0: Wait. We heard there was no more of those. So Correct. Alright. So and if you guys do lose, it will show up on this global leaderboard. Speaker 0: It's attached to a durable object, so don't lose. You'll shame the human race. And here we go. We beat the beat the clankers here. Alright? Speaker 0: And that's pretty much it. If you guys want to get started today oh, in the wrong place. If you guys wanna get started today, I dox.a2b.ai. I maintain documentation of lots of good bunch of goodies, skills, dev tools to get started and, just, you know, basically automate the creation of these tools and maintenance of them on your page. So, yeah, go ahead and, make it happen. Speaker 0: Anyway, that's it for me. Anything else? That's so cool. Alright. Any questions? Speaker 0: Yes. Speaker 1: So question 1 is, if you're implementing things like that in CSS, are you worried about opening a portal to hell? Then the follow-up would be, is there a reason why I know the JavaScript when you're talking in that? Speaker 0: Oh, just for the demo. I just noticed when it was Okay. Try Speaker 1: to find the general limitation. Speaker 0: It's just Yeah. Speaker 1: Exactly. Simply leave those down. Speaker 0: Yeah. Exactly. It gets Speaker 1: it goes a little bit Speaker 0: too crazy with JavaScript. And so, yeah, just making it HTML and CSS. Rendersmizer for the demo. Any other questions? Cool. Speaker 0: Alright, Alex. That was awesome. Thank you for the demo. And go you have to transfer once again. We have 1 more day. Speaker 0: Austin, can you come on down?