A few years ago, we started adapting our websites for mobile devices. Then we adapted them for accessibility. And now we may be about to adapt them once again. This time... for AI agents.
To see what this could look like in practice, I built a completely serious and absolutely enterprise-ready AI CEO Simulator.
We'll come back to our visionary leader in a moment.
BTW, thank you all for the amazing discussion under my previous article. We somehow managed to generate approximately one billion comments 🩷 Many of them were probably smarter than the article itself. The sensible thing to do would be to write a follow-up post summarizing everything.
But honestly, I needed a break from that topic before I exploded.
Sometimes I just have to write something technical, otherwise I'll suffocate. Fortunately, nobody pays me for these articles, so I can do whatever I want 😁 We'll come back to AI in software development another time.
What Is webMCP? 🤖
For now, let's talk about webMCP.
Google is currently experimenting with webMCP support in Chrome, an approach designed to make it easier for AI agents to interact with websites.
The problem it tries to solve is actually quite simple.
Today, when an agent wants to use a website, it has to inspect the page, figure out which elements are important, click around, analyze the results, and repeat this process over and over again. It works, but it's slow, expensive, and not always reliable.
webMCP allows websites to expose structured information about available actions, so agents can understand what they can do without endlessly scraping the page and guessing.
Time for a Completely Serious Business Simulation 🚀
But enough theory.
Let's build something completely serious and enterprise-ready.
@cart0ne mentioned under my previous article that AI had effectively become the CEO of his startup.
So, as a responsible person, I built an AI CEO Simulator in React + TypeScript.
GitHub: https://github.com/sylwia-lask/ai-ceo-webMCP
Live demo: https://sylwia-lask.github.io/ai-ceo-webMCP/
How To Enable webMCP
Before you immediately rush to implement webMCP in your production application, a small disclaimer.
For now, this is still experimental technology. It currently works only in Chrome Canary, Chrome Beta, or Chrome with the appropriate experimental flag enabled.
To enable it:
1. Open `chrome://flags`
2. Search for "MCP"
3. Enable the experimental MCP-related features
4. Restart Chrome
If you'd rather not play with experimental browser flags, that's fine. You can simply look at the screenshots below.
Or click around the application yourself, because everything still works perfectly as a normal website.
That's actually one of the things I like most about this approach. WebMCP is just an enhancement for agents, much like accessibility features are enhancements for users relying on screen readers. Nothing breaks, nothing changes for regular users.