WebMCP: Is your website ready for AI agents?
Search became answers. Now answers are becoming actions. A new browser standard called WebMCP lets your website hand AI agents a menu of things they can do, instead of forcing them to guess. Here is what it is, and why moving early is the advantage.
From ranking, to being the answer, to being the action
For years the goal was to rank. Then AI assistants started answering people directly, and the goal became being the source those assistants trust and name. The next step is already here: people are handing AI agents real tasks. Book this. Compare these. Get me a quote.
When an agent tries to do that on your website today, it has to behave like a confused first-time visitor: read the screen, guess which button to click, and hope it does the right thing. That is slow, brittle, and often wrong. It is the weakest link in the whole experience, and it sits on your site.
What WebMCP actually is
WebMCP is a new browser capability, an API called navigator.modelContext, that lets your website publish its own actions to AI agents as clearly defined, callable tools. Instead of the agent reverse engineering your pages, your site simply says: here are the things you can do, and here is exactly what each one needs.
It was created by engineers at Google and Microsoft through the W3C Web Machine Learning Community Group, announced in February 2026, and opened to a public trial in Chrome in May 2026. Think of it as the difference between leaving a guest to wander your store hoping they find the right shelf, and handing them a menu they can order from directly.
Why this is not just another llms.txt
They solve different problems. An llms.txt file helps AI read and understand your content. WebMCP lets an agent act: run a search, start a booking, request a quote, submit a form. One is about being understood. The other is about being usable. That difference is why WebMCP has real momentum where llms.txt stalled.
Google’s John Mueller recently called llms.txt “purely speculative for now,” and said he likes the WebMCP approach because it has “clear goals and processes.”
Honest status: this is early, and that is the point
We will be straight with you: WebMCP is in a public origin trial, not a finished, everywhere standard. It works in Chrome today and is not yet supported across every browser. We are telling you that on purpose, because being early is exactly where the advantage is. The businesses that get ready before the standard is everywhere are the ones agents will be able to act on first. That is a head start while it lasts.
We did not just write about this. We shipped it.
digilu.com is agent-ready today. We published WebMCP tools on our own site, so a capable AI agent can, for example, run a live AI visibility check on any business directly through us. We built the thing we would build for you, on ourselves first. That is the only honest way to recommend it.
See if your site is agent-ready
We built a free check. Enter your website and it tells you, honestly, whether you expose any agent-callable tools yet. Almost no site does. Yet.