WebMCP: what changes for your business website

Three different things: SEO, MCP and WebMCP

Three mixed-up ideas deserve separation. SEO helps your website get crawled and understood in search engines, without guaranteeing indexing; the same long-standing fundamentals (useful content, correct structure, performance) also feed Google's AI features, which ask for no special file or format.

MCP is a protocol for an AI assistant to connect with external servers and tools. WebMCP, instead, is a proposal for a web page to offer tools directly to the agent visiting it in the browser: checking availability, filling in data or starting a booking, for example. They are different layers and none replaces the others.

What WebMCP is

WebMCP defines how a website registers typed JavaScript tools an AI agent can discover and use during the visit. It includes an imperative and a declarative API, designed as progressive enhancement: the website keeps working for people even where no agent uses it.

Its state is emerging, not standard. The community group's public report (September 2026) explicitly says it is not a W3C standard nor on the standards track. Chrome offers an origin trial from version 149 and, separately, experimental local enablement. There is no global index guarantee nor universal browser or agent support.

What an agent needs from your website today

Before thinking about agent tools, your website must do the basics well: explain each service clearly, show visible contact, load fast and use correct titles and structure. An agent, like a customer, fails on generic texts and confusing navigation.

The next step is structured, machine-readable content: consistent data between what is visible and what is marked up, differentiated pages per service and real frequently asked questions. This helps SEO and quoting assistants today, regardless of what happens with WebMCP.

Security and human confirmations

Exposing tools to agents demands care with inputs, results and consequential actions: bookings, payments or data changes. Security guidance recommends delimiting what each tool may do and asking human confirmation on what matters.

For a small business the rule is simple: an agent may consult and prepare, but committing actions (charging, booking, deleting) get confirmed by a person. Design limits first, capabilities second.

What to do this year

You do not need to adopt WebMCP today, but you should leave your website ready: clear content per service, correct structure, performance and visible contact. If you later expose agent tools, you will build on a solid base.

We follow this technology closely and will apply it where it makes sense, as progressive enhancement and without selling it as a standard. Our own website makes no claim to expose active WebMCP tools: when it does, we will say so just as clearly.

One clear page per service, with visible contact
Correct titles, descriptions and structure
Consistent content between visible and structured data
Consequential actions always confirmed by people

Related services

Modern business websites

Sources

Back to all insights