WebMCP: What a Small Business Site Should Do Now

You hire a plumber, and the plumber's website has a quote form. A person finds it, fills it in, done. Now picture an AI assistant doing that errand for the customer: it lands on your page, sees a form with fields labeled "Field 1" and a button that's really a styled paragraph, and has to guess.

WebMCP is a proposal to stop the guessing. It's early, it's experimental, and most small business owners should not be rebuilding anything over it. But the cheap prep is the same prep your site needed anyway.

What WebMCP is

Today an AI agent that wants to do something on your site (book a slot, request a quote, check stock) mostly works like a very fast, slightly confused visitor. It reads the page, or looks at a screenshot of it, and tries clicks until something happens.

WebMCP lets the site speak first. The page registers a short list of named actions, each with a plain description of what it does and what it needs. The agent reads the menu and calls the action it wants.

Chrome's announcement describes two routes:

• Declarative: for standard actions that already live in an HTML form. You annotate the form you have.
• Imperative: for anything dynamic that needs JavaScript behind it.

If the word "MCP" rings a bell, don't mix them up. Anthropic's Model Context Protocol connects an AI app to a service from the back end. WebMCP runs in the browser, in the tab, while someone is on your site. Similarweb's explainer says the two can coexist.

Where it stands today

Read this part twice, because the hype will skip it.

• It's a proposal from the W3C's Web Machine Learning Community Group, developed with Google and Microsoft, per Similarweb's summary.
• Chrome's own post says it's available for prototyping to early preview participants.
• Similarweb reports it's reachable only in Chrome Canary behind a testing flag, and that Firefox and Safari haven't signaled plans. That's a secondary source, so treat the specifics as a snapshot and check Chrome's documentation before you act on a version number.
• The same piece says general availability is expected mid-to-late 2026. Expected is not shipped.

So no, your customers' assistants are not calling WebMCP tools on your site today. Nobody should tell you your visibility is at risk for skipping a developer trial.

Why it's still worth a look

The direction is clear even if the spec isn't. More of the web's errands are going to be done by software acting for a person. When that happens, sites that make their actions legible will be easier to work with than sites that don't.

Think of it as the next layer on a stack you may already be building. First, agents have to be able to read your page, which is the ground covered in how AI agents read your website. Second, they have to be able to do something once they've read it. WebMCP is a proposal for that second step. Both sit under the bigger picture in our guide to Answer Engine Optimization (AEO), the work of being the business an AI answer names and can act on.

There's also a measurement wrinkle. Similarweb's piece suggests watching for odd direct-traffic patterns on conversion pages, since agent-driven actions may not look like ordinary sessions. That fits the broader problem of telling AI-agent visits from human ones.

The cheap prep that isn't a bet on WebMCP

You don't need Canary or a flag for any of this. It's the unglamorous work, and it pays off whether WebMCP ships, changes shape, or fades.

1. List your three to five money actions. Request a quote, book an appointment, call, get directions, buy. If an agent could do only one thing on your site, which one earns you revenue?
2. Make each one a real HTML form or link. A quote request built from a native form with labeled fields is legible to a person using a screen reader, a crawler, and, if the proposal lands, a declarative WebMCP annotation. A form faked out of styled divs is legible to none of them.
3. Label things like a human would read them. "Your name," "Best phone number," "What do you need done?" beat "Field 1." Plain labels are the closest thing to a tool description you already write.
4. One job per action. A single form that books, subscribes to a newsletter, and asks a support question is hard for people and harder for software.
5. Keep confirmations for anything that costs money or commits you. Similarweb's guidance is to require user confirmation for consequential actions and to validate every input an agent sends. Good advice for forms in general, since your existing forms already get junk from bots.
6. Run on HTTPS. Similarweb notes WebMCP requires it. Your site should be on it regardless.

Where not to spend money yet

• Hiring someone to "implement WebMCP" now. There is nothing stable to implement. A developer trial can change under you, and you'd be paying to track a moving spec.
• Buying a plugin that promises "agent-ready" status. If it can't point to a spec version and a browser that supports it, it's a badge.
• Treating it as a ranking factor. Similarweb reports no such link has been announced. Anyone selling you rankings through WebMCP is guessing.
• Letting an agent submit anything unattended without checks. An action that charges a card or books a crew should confirm with a human first.

What to do this quarter

Check your key forms. Open each one with the keyboard only, no mouse, and see whether every field has a label and every button is a real button. If you can't complete your own quote form that way, a machine will struggle too. That's a one-afternoon audit, and it's the kind of thing a monthly care plan should be catching before it becomes an expensive redesign.

Then park WebMCP on a watch list and revisit when Chrome moves it out of preview. If you'd rather have someone watch that for you, that's part of getting found on Google and AI at The Digital Back Office.

FAQ

What is WebMCP in plain English?

It's a proposed browser feature that lets a website tell an AI agent, in a structured way, what actions it offers, such as "request a quote" or "check availability." The agent calls the action instead of scraping the page and guessing which button to click.

Is WebMCP the same as Anthropic's Model Context Protocol?

No. Anthropic's MCP connects AI applications to services from the back end. WebMCP is a browser API that runs client-side while someone is on your page. Similarweb's explainer says they are complementary.

Can I use WebMCP on my site today?

Only for experiments. Chrome's announcement describes an early preview for prototyping, and Similarweb reports it needs a flag in Chrome Canary. It's a developer trial, so the API is expected to change.

Will WebMCP help me rank higher in Google?

No such link has been announced, per Similarweb. Treat any claim that it boosts rankings as speculation.

Do I need a developer to prepare for it?

Not for the basics. Audit your key forms for real HTML form elements, clear labels, and one job each. A developer becomes useful once the standard is stable and your site has complex, JavaScript-driven actions.

Does this matter for a site that's just a brochure?

Less. If your site's main action is a phone number and a contact form, clean labels and a working form cover almost everything. WebMCP matters more as sites add booking, ordering, and account features.

How would I know if AI agents are already using my forms?

Probably not through a WebMCP signal, since it isn't live for visitors. Watch for unusual direct traffic on conversion pages and read your form submissions for patterns that look automated.