Speaker 1Think about this. AI agents are about to become a new kind of visitor on the internet, and I think billions of dollars of wealth will change hands in the process. Because millions of AI agents are going to be browsing and buying on the internet, but the internet isn't designed for them to do that. And that creates a really interesting question, which is, what does an agent-ready website or app look like? And how do you actually build one? Well, there's this new little thing by Google called WebMCP, and I'm honestly surprised more people aren't talking about it. The simple idea is that websites can expose cleaner actions for AI agents. So instead of an AI agent trying to figure out a page like a human being, the site can basically tell an agent, here's how to search, here's how to book, here's how to buy. So today I have my friend Vinny come on and just clearly explain what WebMCP is, how it differs from MCPs, why it matters, and how it works. And I give you two startup ideas that I think could cash flow that you can start today. Enjoy the episode. I hope it gets the creative juices flowing. And if you haven't liked, commented, and subscribed, what are you doing? This stuff should be paid. We make it free. I just want to see you win. Let's go, and I'll see you at the end of the episode. The MRR gods. Vinny is back on the pod to explain something very, very, very powerful. WebMCP. Vince, you actually brought it to my attention. Vinny, by the end of this episode, what are people going to learn?
Speaker 2All right, they're going to learn how to use WebMCP, which is kind of exactly like it sounds. It's MCP, but in the UI, in the browser. And this is like a brand new experimental feature from Google and Microsoft. So I really think this is effective. First mover advantage here. So if you can learn this stuff, you're really bringing, you're getting the skills that you need to bring stuff to market that is emerging, that's going to probably be the next big trend. So I think this is a really cool thing.
Speaker 1So Vince is going to actually explain to you in a clear way what WebMCP is, how to use it. And at the end of the episode, I'm going to share with you two startup ideas, cash flowing startup ideas that I think could use WebMCP that you can build today. That'll be at the end. Vince, you start them off.
Speaker 2All right, cool. So let me start from like a problem I had myself. When I heard about WebMCP, the first thing that came to mind is this shop that I've got here. It's an espresso machines and gear shop. So I was buying an espresso machine and it has like a lot of specifications. It's got a lot of gear and accessories and figuring out which one's right for me and also which accessories fit was kind of a pain. So it was a lot of back and forth Googling, also putting stuff into an agent or chat GPT or whatever. And like, does this fit? Will this work? So I thought, oh, cool. This is a great use case for something like this where we could build a shop with WebMCP tools in it that your agent can talk to. So you can bring any agent that you're using, which is whether it's like Claude Code or chat GPT, cowork, whatever these whatever agents are. Out there, maybe Grok bought and you can talk to the website and ask it stuff. So let me just show an example real quick. And so I want to upgrade from my current Mara X machine and I want to get one that's able to make two flat whites a day easily and fits on my counter space, which is about 32 centimeters wide.
Speaker 1By the way, in simplest, like in the simplest form, correct me if I'm wrong, Vince, but WebMCP is basically just websites with agents. So you're making websites agent readable and agent actionable. Is that right?
Speaker 2Exactly. And it's not like this wasn't available before, but it was available in a lot like clunkier way. So you've got computer use or you've also got agents that can kind of browse and use a browser and go through websites, click buttons. But before they had to do it in a very not so efficient way. So they're they're getting the entire DOM, which means. They're getting all the code from the website and they're like scanning through it and finding where to click, taking screenshots and stuff. But look at that. What just happened right here on the screen. It manipulated the the website, was able to find two machines, put them side by side, and then it highlighted really cool feature, highlighted what features or what specs about the machines fit my request that I just had. So it's like the port of filter fit, which is going to fit like an accessibility. You have and then will it make the two flat whites like you asked and does it have the right width? Will it fit on your counter spot? So, like, that's really cool. And before to do all that, well, first of all, it wouldn't be able to manipulate a page in this way as easily and also would have to go through all this scanning all this code reading, whereas this now with WebMCP, there's a set of tools like the ones that are just popping up on the screen here. And those are the ones that you make available to the agent. So it gives it a real. Really efficient, concise list of things that it can do on the website, and it knows how to do that and it can just do it easily and you can do some really cool, creative stuff with this.
Speaker 1Yeah, and I think like one of the reasons I think this actually matters is if you think about SEO, right, it was like, can Google understand the page? And then we had a which is can I cite the answer? And now we're entering this WebMCP era, which is basically. Can the agent finish the job? And we're what we're learning is that websites aren't really optimized. And I think that's why Google and Microsoft decided to build this thing. Right. Because they don't want a broken Internet to exist. And I think as like a founder, like, why does this matter is because there's there's, you know, billions, billions of dollars changing hands on these tools. Right. Or on the Internet. And if we can optimize. Some of these websites, you know, there's just there's a lot of opportunity.
Speaker 2Yeah. And I think, I mean, maybe the people like you and I and the people listening, they're more agent native or they're more this kind of early adopters of new technology. But we have to remember that the Web has been around for a while. People are used to you eyes and browsing websites and stuff like that. And people don't really want to. The majority of Web. Users don't want to use just like a CLI tool or an agent in the terminal like this. They want to be able to interact with something visual. So this Web MCP really makes it the best path to do that. So we'll really allow for kind of normal than average consumer to adopt agent tools. So it's kind of like meeting them in the middle. Right. With the new agent technology and the stuff that they're used to.
Speaker 1Cool. What else do we need to know about it?
Speaker 2So like one of the big things is, like I said, is that it's not scraping and parsing the entire DOM. So it doesn't have to. It's more efficient in the way it works. But the other thing that's really cool is that these tools, you can make them conditional. So like you see here in this list, we have tools that are always available versus logged in. This is all happening through the browser session. Right. So I've logged in. You can see I'm up here. I've logged in. These are the tools available. And if I log out. Well, then we'll see. There's only three tools available now. Right. So this is really cool because one of the big hurdles to doing other kind of agent native approaches like an MCP server or an API is that you have to deal with tokens, credentials, people sending and sending their their identity through, you know, API keys and tokens and things like that. Whereas this you just log in. Right. So I can. Log in with my username and password and it has access to the entire browser session there. So the fact that I'm logged in, the agent has to doesn't have to do anything special. We don't have to connect an MCP server and authenticate and all that stuff like you have to do with, you know, a typical MCP server or with an API or things like that. So it's like the least technical approach to making an app or a website or a Web store agent native. But with the most flexibility and the most features. So this conditional tool calling, all this stuff just happens because of the browser state. And that's a really nice thing.
Speaker 1Yeah, that's really cool. That's just like built in. I mean, it makes sense, right?
Speaker 2Yep. It's using the whole browser session. So that's really nice. All right. So I saw this tweet the other day and I've seen this going around a lot where people are saying, I don't want to use your products agent. I want my agents to be efficiently enabled to use your product. And that's exactly what we're getting with web MCP and especially for things like web stores and stuff like that for e-commerce or maybe even, you know, other examples that we'll look at later that you that you have prepared for us. So this is this is a sentiment that's going around on Twitter a lot lately. And what does Dylan from Cloudflare mean by this? So we have these like different ways an agent can meet an app. Right. And let me go zoom in real quick because we have a lot. And they're going from headless. You see at the bottom here, it says headless. So basically. running an app via your agent without ever seeing the app that's what headless means right there's no app in the browser there's no website so you bring your own agent you can hit a raw api but there's like we said there's lots of things you have to deal with authentication and the agent has to hold an api key and things like that but then you can bring your own agent and you can use mcp which is a typical mcp server but that's another layer on top of your app's back end and then your agent can't manipulate the ui right like we just saw so those are completely headless ways they're a little add a little bit more complexity to your to your app or to your product now we have computer use which is where the the bots or the agents literally have a computer that they can use whether it's your local computer or a computer in the cloud and they're running through screenshotting stuff and clicking stuff on the computer on the ui like you would and this isn't really the most efficient because of like we said before you've got to go through you've got a screenshot or the agent has to screenshot all this stuff so this is slow and fragile at the moment we have browser mcp which is similar to computer use where like we were talking about where you get the whole code from the website and it has to kind of figure out through the html code and where it can click and what it can do again that's a little bit more complicated than what you're used to and it's a little bit more complicated than what you're used to but it's a little bit more complicated than what you're used to and it's a little bit more complicated than what you're used to and it's a little bit more complicated than what you're used to and an in-app agent which is what the tweet was complaining about right which is that like you build an app with a little uh agent sidebar and you're um the agent in that app is the only thing that can communicate and deal with it right so what they're saying is they want something where they can bring their agent and and they can use your product if they want to and they can use efficiently and that's where i think especially for traditional apps with a front end storefront whatever that they can then use bring their agent and use your app efficiently so that's what's really
Speaker 1cool about it does that make sense so if i'm getting this right so web mcp you've got your agent there's a set of tools or things that you can do basically on the website or the app and then and it's sort of limited to what you're using and what you're using and what you're using and the in-app agent you have your you know the the vendors agent and um the apps agent right and that just interfaces with the apps logic and data back and forth and the app is like isn't that like the the best end state of of where we think things are going right the in-app agent you mean yeah
Speaker 2well i mean you can look at it from two different perspectives right that uh it's nice to have like a little um in-app agent there but um you're responsible then for configuring everything you're responsible for the tokens right you're responsible for setting it all up whereas with web mcp web mcp is like this really nice middle ground where you don't have to work you don't have to pay for tokens you're giving the app agent capabilities but the user is bringing the app the agent that they used and any agent will work with it so uh if we're moving quickly to this world where everyone has an agent that they use at work that they that they use for personal preference you know um you don't have to then separate them from that that's the agent they know and they can just use it with your tool via web mcp so it's kind of like the nicest because it makes it easy for you and it makes it most comfortable for them
Speaker 1yeah i guess the in-app agent was sort of like a transitionary piece of software um that needed to exist for a certain amount of time but we're like kind of growing out of it like the idea of like you know you use you know intercom fin right which is basically like i think a customer support agent like that experience is really really good um but now in a world where it's pretty clear that over the next 24 36 months everyone consumers are going to have their own agents it just makes sense that these agents are going to need places to interface with the internet at large and the internet is just not designed for those agents yet so you know that's why web mcp you know exists yeah i think there is a place for in-app agents
Speaker 2right like if in notion for example they offer both but like if there's something that is like cloudflare dashboard they have an in-app agent and this is so it's like very it's gated to only use their um their tools and not to change preferences too much so that you don't do anything kind of hazardous i can see where in-app agents might make sense but we're moving into this world where it's like we're doing so much with agents and we want them to keep their context so you want one tool that kind of has the context and knowledge and memory of everything that you do and to be able to bring that one agent with all that context to different tools is really powerful and i think that's where you're going to see people they're going to kind of get stuck on one agent one kind of product whether that be grokbot or claude co-work or chat gpt work or whatever and then they're just going to kind of access the internet and and interface with the with different things on the internet through those agents so that's where i think web mcp is really powerful it's also just like a great companion for when you're shopping with for complicated things you can use an agent if you need to kind of help you out figure out which specs what things right and you don't have to build in this big bloated you know in-app agent into your into your app to get some better customer experience for you can you show an example another example yeah sure so um i could say like yeah so you suggested the lit bianca what are some really nice accessories i should add that will fit the lit bianca so this is something that like bugged me a ton was i found the machine now i need a grinder now i need a filter i want a new basket they're all different sizes they all use one might use a measurement one might use a name or or some kind of like brand name and parsing through all that information as a customer can get really tedious so just to have an agent that can do that and then let you know is perfect because it has all the context here from the store it knows what i've ordered it has different tools here like if i scroll over here it can see get my gear is one tool so it knows what i've ordered from here it knows what i've ordered from here it knows what i've ordered here um it can get the cart it can add coupons right so it can apply a coupon on checkout and all this stuff so here it's just saying the first thing you should buy is this lit water softener two pack so i'll just say cool add that to my cart that sounds great right so the nice thing is is that i could tell it highlight that on the ui or i can just say you know whatever i like the sound of that go and and add it to the cart and it'll do all that stuff in real time and i have visual of that i can see the things right and um i think that's pretty cool that's really cool i mean come on that's really cool yeah so um and even tell me here you have softener is in uh you have a barista 10 coupon 10 adding it for the rest so i don't know if it's just because i'm a coffee aficionado
Speaker 1you know i love coffee you know you can see my coffee setup back there yeah um that this is just hitting for me so hard but like to me it's like it makes so much sense like we're as customers we're going to be using agents we're going to want them to go and do stuff for us we want to make sure that the things that they do it actually is able to complete the tasks um and to see this work just so seamlessly
Speaker 2just is awesome yep yeah it's really cool i think so this is a great example but you can think about anything where it kind of gets complicated uh you know technical stuff um if you're buying hard like hardware and i don't know you need to uh you're doing like hardware hacking and you need to write the right battery for for the uh development board or car stuff and you need the right parts like all this stuff that can be really complicated like that this is a great use case i mean i'm just
Speaker 1curious you know where mcp in your mind where mcp fits which i think is like another way of saying you know how do you like in which sectors niches should you be implementing web mcp because there's going to be a lot of people that are going to be like oh i don't know i don't know i don't know like some some industries are going to be last to implement it right and i think from a founder perspective i care about the the ones that have the highest priority so which are those and why
Speaker 2do they matter yeah yeah i think like like i said these compatibility driven commerce right so it's like all those things camera systems any kind of web web store that's complicated that'll be a sass admin so like any kind of admin board or console or analytics or marketing tools you can add these things in to make it easier for you know your marketing team to to deal with these things and and set up features and stuff like that and even like regulated industries like the nice thing is is that you can't use api keys so you don't want to go to you don't really want to use mcp servers or apis you maybe want to set up a few and that's a great thing about web mcp it's like a few tools that you can use and you can use a few tools that you can use and you can use a few that are using the browser state that can be read-only so they don't actually touch anything. So let's imagine like insurance or banking self-service. Like you could set up some WebMCP tools that are read-only or only touch very non-sensitive settings. And then that will help the user figure out where they need to go to enter something or where they need to go to get the right information or it can even summarize and pull the right information for them via their agent. So stuff like that. I even think internal tools. So building internal tools at a company. So if you're like an entrepreneur, you don't necessarily need to use WebMCP right away for your customers. There might be a really great solution for you in-house. Like your internal tools, stuff for yourself, for your employees. That's where I think there's a lot of potential.
Speaker 1I love it. All right, let's go to some business ideas that people can implement. I'm curious your take on it too. So let me share my screen. All right, Vinny. So WebMCP is here. I wanted to come up with two business ideas that I think are cash-flowing that I think anyone non-technical can set up or somewhat non-technical. You just don't need to be like a hardcore engineer. The first idea is a WebMCP conversion agency. And I bet you there's probably some domains that are available like webmcp.agency or something like that. That someone can go and grab right now. So the big idea is how can you make boring business websites agent-ready? So you have these boring businesses like law firms and home service and HVAC, med spas, dentists. And you just go and create these V1 tools for them. So that can be like requesting a quote or booking consults. And you're just selling them on this idea that there's going to be, a new class of citizens on the internet. These are going to be these AI visitors. And these AI visitors, these agents, are going to book jobs, right? So you sell them on maybe a $2,000 to $10,000 setup. And then you charge, you know, it could be $500 a month or a few hundred dollars a month, $700 depending on who it is. Is it a big law firm, a small law firm? On monitoring and evals, and then you build this retainer that, you know, is building cash flow every single month. Um, and you just update it and that sort of thing. What do you think of this idea?
Speaker 2Yeah, I actually think it's a really good idea. Um, I see stuff on the web floating around where they're showing that, uh, things like you said, uh, dentists or law firms are starting to use agents at their offices. And so I think they'll get it. And it's good, uh, that you bring this up because I think it's worth mentioning that WebMCP is an experimental feature in Chrome right now. So it launched in February. Join effort from Microsoft and Google, but it's still in early days, but that's why I think there's real potential here because we talked about this package. I showed the diagram of, you know, from headless to, um, bound to UI, the different types of agent native, uh, approaches you can use to, um, connect to apps, right? So you could do this as a package where, um, it's not only WebMCP, but other tools, maybe a MCP server for them. And you tell them that like, look, this is new emerging stuff, or you're learning this because it is this new emerging stuff so that when it does get adopted, you're the first mover, you have the first mover advantage. And so you can sell it as a package. Like we'll, we'll put in MCP, we'll put in WebMCP, um, we'll, we'll create, um, you know, whatever, all of this stuff that, that aligns with their vision, you can make whatever they want available and you can show them the different approaches you have that one that uses a UI. One that is headless and you're the expert there. And that's the way that you, uh, make money. Yeah.
Speaker 1Maybe it's just agent conversion agency. And then WebMCP is just one of the technologies that you use. Yep.
Speaker 2Or like we were saying before internal tools, it doesn't only have to be about, uh, customer facing stuff. You can show them how they can make processes in their office better for them and their employees using stuff like WebMCP.
Speaker 1Totally. Cool. Uh, startup idea number two, I'm calling it the agent mystery shopper. So it's testing whether agents can complete the most important user journeys. So if you think about a user journey, maybe it's a Shopify store, you know, you want to buy a hoodie. If it's a, you know, consulting company, it's booking a consult. If it's an insurance company, you're filing a claim, requesting quotes, you're ordering items, all these different things that you want the agent to do. So the agent. Is going to run a bunch of tests and you, the customer get a report back. Where did the agent get stuck? Were there bad descriptions where they're missing tools, conversion risk, and then you're basically selling, you know, uh, agent reports, maybe it's monthly, weekly, and you turn the repeated fixes into software. So I like this business because it's pretty simple. Um, it's almost like, um, you know, just, uh, uh, a report, like a credit report almost on. You know, how your, how your, your website and your apps are, uh, around implementing things like web MCP. Um, and then you can charge a few hundred dollars a month or a hundred dollars a month for something like this. What do you think about this idea?
Speaker 2Yeah, I think also a cool thing. It makes a lot of sense. And the cool thing is, is that you can even pair approaches like this to your, uh, agent, uh, conversion agency, right? So it's like you can go and run these agent tests and evals and you can be, and you can show them that, Hey, this is a good idea. Hey, this might work better if you used web MCP on top of it. You're only using X. Why not check out this as well? So you can kind of combine the approaches with, uh, I think here. So that's a really cool idea.
Speaker 1I like it.
Speaker 2Yeah. So I just also wanted to mention that, um, I showed a couple examples here, but there are 16 different tools that you can, uh, use, um, with your agent via web MCP on this example, uh, espresso machines and gear store. And you can do that right now. You can go to. Uh, crema and co, uh, client flight at dev we'll put the URL and the show notes and stuff. Um, and you can test it out there. One thing you should know is that, like we said, it's experimental stuff early days. So go into Chrome flags, enable web MCP support and go into Chrome inspect and allow remote debugging. So these are the things that you will want to enable so that you can start using these experimental features. And if you want to build your own app like this, you can also click on. The, um, GitHub repo button down there next to the web MCP tools pill, and you can clone this repo and you can play around with it, make your own version, whatever it's free for you to start playing around with cool business ideas. So those are two important, uh, things I think are, uh, worth mentioning and yeah, I would be, it would be cool to see what other people do with this repo, what other people do with these ideas. Um, so people should definitely share those online with us. I think that'd be awesome to see.
Speaker 1Yeah. We'd love to see it. I think, you know, I, there's, I can just see the comment, uh, of someone saying, well, it's an experimental, it's, you know, it's so experimental, like it's so it's way too early. Like why even bother playing with this stuff? And I, you know, you know me, I love playing when things are experimental because when, you know, the arbitrage exists when, when it's experimental, like I love trying things, getting my hands dirty and, and, and seeing what I can build now. Because when it's going to be, you know, super popular, that's when that window starts closing.
Speaker 2Yup. Definitely. Think about when chat GPT came out or when GPT, I think it was GPT two and three came around and people were playing with it and going, ah, it was just two years before chat GPT launched. And people were going, ah, this is crap. This is, we're way off. We're years away from AI being like a serious thing, a serious tool. And then boom, the explosion happened just a year or two later. Like shouldn't pass this stuff off as, you know, just like experimental stuff. That's not going to get implemented. I mean, we're talking about Google here. They have pretty good foresight. This is something that they've been talking about for a few years now. They made the proposal two years ago, they launched it at the beginning of this year. So I wouldn't, I wouldn't fade this personally and I'm excited about it. So that's enough for me.
Speaker 1All right. Thanks for coming on Vince, sharing the sauce and I'll see you next time.
Speaker 2Yep.
PodcastTranscript AI