Overview
Humans are no longer the only ones looking at your website.
On August 7, 2026, Cloudflare announced the developer preview of WebMCP. The pitch: with one switch, any site becomes usable by browser AI agents — no new APIs, no origin changes. We saw the announcement and enabled it on andoor.co the same day. The work took one toggle. Verification included, less than an hour.
This is a field report. What actually happened, and what changes from here — measured, not imagined.
What WebMCP Actually Does
Your site stops being something to read and becomes something to operate.
To an AI, a website has always been a wall of text. An agent trying to use a site had to parse the screen and guess where the buttons are. Slow, and fragile.
WebMCP lets the site itself tell agents what it can do. It brings MCP — the Model Context Protocol, the standard that connects AI to tools — into the browser.
The clever part of Cloudflare’s implementation is that everything happens at the edge. One script gets injected into the HTML at delivery time. The origin code is never touched.
Was It Really “One Switch”?
It was. A single toggle in the dashboard, and it was done.
The entire procedure: open your zone in the Cloudflare dashboard, go to Agent Readiness, find the Labs section, turn WebMCP on. No deploy, no code change, no DNS change.
What we measured immediately after:
- A 47KB bridge.js was auto-injected into every page — the top page, the English pages, every subpage
- Zero console errors. No interference with existing analytics
- No CSP changes required. Same-origin delivery means even a strict Content Security Policy passes as-is
- On unsupported browsers, it silently does nothing. Zero impact on regular visitors
“No origin changes” turned out not to be marketing exaggeration.
But Nobody Is Coming Yet
The site is ready. The agents are not here yet.
Right now, the only browser with the WebMCP API is the latest Chrome behind an experimental flag. So even with andoor.co agent-ready, almost no agent will actually come use it today.
Does that mean there is no point in hurrying? We think the opposite.
The asymmetry is the whole story: the site side can go first at near-zero cost. The moment agents become mainstream, a gap in experience opens between sites that are ready and sites that are not. It is the same structure as SEO. The ones who placed their sitemaps before the crawlers arrived were the ones who got ahead.
If optimizing to be read by search engines was SEO, what comes next is designing to be used by agents. The name for it has not settled yet. The structural shift has already started.
Why We Moved on Day One
Words about technology you have not touched are all borrowed words.
ANDOOR’s banner says: AI and humans, as one, inventing systems and shipping beautiful products. Under that banner, saying “apparently something called WebMCP came out” is not an option.
We enabled it on our own site, read the injected script, verified CSP compatibility, and measured the behavior on unsupported browsers. Only after all of that can we tell a client, in our own words, whether to adopt now or wait.
We do not put developer-preview technology into a client’s production site. That is not boldness; that is failing to distinguish experiments from adventures. Try it on your own site first. The only castle you are allowed to break is your own.
We ship. We own. That one hour on announcement day was the practice of it.
Takeaways
- WebMCP is the standard that turns websites into tools for AI agents. Cloudflare shipped a preview you can enable with one switch
- Measured on andoor.co: adoption cost is near zero, side effects on the existing site are zero
- Agent adoption is still ahead. But the site side can get there first, today, for free
- Touch it before you talk about it. Keeping that order is what gives words their weight
The era when only humans stood on the other side of your website is ending.