More and more website visitors aren’t people. They’re AI agents acting for people: booking a table, comparing prices or requesting a quote. Google has proposed a new standard, WebMCP, to help these agents use websites properly. It may quietly change how websites are built.
Today, most agents work the hard way. They take screenshots of your page and guess which button does what. Then they click where they think the right field is. As a result, the process is slow and expensive, and it often fails.
Here’s what WebMCP is, where it stands today, and what we think business owners should (and shouldn’t) do about it.
What Is WebMCP?
WebMCP is a proposed open web standard. It lets a website tell AI agents, in clear and structured terms, what it can do and how to do it.
Instead of guessing its way through your contact form, an agent can call a “tool.” A tool is a clearly labelled action, for example:
request_quote: takes a name, email, project type and budget- book_table: takes a date, time and number of guests
- search_products: takes a keyword and a price range
The agent reads the tool’s description and fills in the right inputs. Then your site does the work, using the same logic and design it already uses for people.
In Google’s words, tools let sites “instruct agents exactly how and where to interact with your site.”
Is WebMCP the same as MCP?
Not quite. The name borrows from the Model Context Protocol (MCP), a popular standard that connects AI assistants to back-end systems. However, WebMCP runs inside the browser, on the page itself. It uses the visitor’s existing session, so the user can see what’s happening. In short, it’s MCP’s front-end cousin.
How WebMCP Works: Two Ways to Expose Tools
WebMCP gives developers two approaches.
1. The declarative API (HTML forms)
For many sites, this will be the easy win. You add a few attributes to forms you already have, and they become agent-ready:
html
<form toolname="request_quote"
tooldescription="Request a project quote from TERAX for a website, brand or online store.">
<input name="email" type="email" required>
<select name="service" toolparamdescription="The service the client is interested in">
<option>Web Design & Build</option>
<option>Branding & Identity</option>
<option>E-commerce</option>
</select>
<button type="submit">Send</button>
</form>
Note: these attribute names come from the current draft. They may change before the standard is final.
2. The imperative API (JavaScript)
For richer interactions, developers register tools in JavaScript with registerTool. Each tool has a name, a description, an input schema and a function to run. This suits complex flows, such as configuring a product or planning a trip.
Either way, the tool runs visibly on the page. Sensitive actions, such as payments, can still ask the user to confirm.
Why WebMCP Matters for Businesses
1. Agents will prefer sites they can understand. When an agent compares two suppliers, it will finish faster on the site that explains itself. One early implementer reported up to 90% fewer AI tokens when agents called tools instead of reading the screen. Cheaper and more reliable means more likely to be chosen.
2. Big brands are already testing it. Google named Expedia, Booking.com, Shopify, Etsy, Instacart and Target among the early testers. Redfin, Credit Karma and TurboTax are on the list too.
3. Google’s own assistant is coming. Google has said Gemini in Chrome will soon support WebMCP. When that ships, millions of Chrome users will have an agent that can use your tools directly.
4. You keep control of the experience. Screen-scraping agents use your site however they like. With WebMCP, by contrast, you decide which actions are exposed and how they’re described. You also decide what needs a human to confirm.
Where WebMCP Stands Today (October 2026)
We want to be clear here, because a lot of the online hype isn’t:
- It’s still experimental. WebMCP is a draft from a W3C community group, edited by engineers from Google and Microsoft. It is not a finished standard.
- Chrome is testing it. A public origin trial began in Chrome 149 and is scheduled to run through Chrome 156. An early preview first appeared behind a flag in Chrome 146, in February 2026.
- The API is still moving. For example, the JavaScript entry point recently moved from
navigator.modelContexttodocument.modelContext. So tutorials from early 2026 are already out of date. - Other browsers aren’t on board yet. Edge has experimental support behind a flag. Firefox and Safari have made no commitments.
- Few agents use it yet. Real-world usage is close to zero. That will change once Gemini in Chrome starts calling WebMCP tools.
Security matters, too. Tools run with the user’s logged-in session. Therefore, an agent tricked by prompt injection could misuse a badly designed tool. Good tools are narrow, clearly described and read-only where possible. They also ask for confirmation before changing data or taking payment.
Our Take: How to Prepare for WebMCP
At TERAX, we don’t rebuild websites for every new acronym. But we do build websites that are ready for what comes next. Here’s the sensible path:
- Don’t rush to production. Unless you run a large store or booking platform, you don’t need WebMCP live today.
- Fix your forms first. The declarative API rewards clean, well-labelled HTML forms. Messy plugin output confuses agents and people alike. The same goes for heavy plugins doing jobs they weren’t built for (see why we say stop overusing WooCommerce).
- Know your key actions. List the two or three things visitors most need to do on your site. For example: booking, requesting a quote or finding a product. These will become your first tools.
- Keep your site fast and well structured. Agents favour pages that load quickly and are easy to read. So do people and search engines. Here’s how we scored a near-perfect 96.
- Choose a stack that can adapt. Modern WordPress on the Block Editor is a good base. With custom code instead of a pile of plugins, adding tools later is simple.
For the technical details, Google’s WebMCP documentation is the best place to start.
The Bottom Line
WebMCP is an early but serious signal. The web is gaining a second audience, AI agents, and websites will need to speak to both. The winners won’t be the businesses that rush. Instead, they’ll be the ones whose sites are already clean, fast and well structured when the switch flips.