What Is WebMCP? A Plain-English Guide for Website Owners (2026)

AI agents are starting to do things on websites for people: compare products, find a service, fill in a form. Today most of them do it the hard way. They look at the page, guess which button does what and click, much like a person using a website for the first time. WebMCP is a new web standard that gives them a better way in. This guide explains what it is, in plain words, and what it means for your business.

What WebMCP is

WebMCP stands for Web Model Context Protocol. It lets a website describe a few useful actions as tools: each tool has a name, a short description and a list of inputs. A shop might offer search_products with inputs for price, size and colour. A clinic might offer find_appointments with a date and a service.

When a visitor uses an AI agent in a browser that supports WebMCP, the agent can see those tools and call them. Your website runs the tool with its own code and sends back clean data, such as a list of products with prices and stock. The agent then shows the visitor the answer.

Think of it like the difference between giving someone a tour of a messy warehouse and handing them a well-organised catalog with an order form. Both work, but one is faster and makes fewer mistakes.

Why it matters for businesses

• Fewer wrong answers. Agents get your real prices, stock and opening times from your data, not from guessing at the page.
• Less breakage. A theme update, a pop-up or a moved button can break screen-reading agents. A named tool keeps working.
• You stay in control. You decide which actions exist, what they return and which ones need the visitor’s approval.
• An early lead. Very few websites offer WebMCP tools yet, so adding them now puts you ahead of competitors.

How it works, in three steps

1. The website registers tools. Either by adding two attributes to an existing HTML form (the declarative API), or with a few lines of JavaScript that call document.modelContext.registerTool() (the imperative API).
2. The browser tells the agent. A compatible browser lists the page’s tools for the AI agent the visitor is using.
3. The agent calls a tool. Your code runs in the page, with the visitor’s normal session and permissions, and returns the result.

A declarative tool can be as small as this:

<form toolname="search_products" tooldescription="Search the store catalog by keyword and maximum price." action="/shop">
  <label for="q">Search</label>
  <input id="q" name="q">
  <label for="max">Max price</label>
  <input id="max" name="max_price" type="number">
</form>

When an agent uses this tool, the browser fills in the form and shows it to the visitor. By default the visitor still presses the button.

Browser support in 2026

WebMCP is new. In 2026 Google made it available in Chrome as an origin trial, a way for sites to try a feature on real visitors before it becomes a standard. Developers can also turn it on with a Chrome flag for testing. Firefox and Safari have not announced support. The API is still changing: in 2026 it moved from navigator.modelContext to document.modelContext.

That means two things. Browsers without WebMCP simply ignore it, so adding it carries little risk. And it is early, so treat it as preparation, not as a source of sales next month.

Is it safe?

A WebMCP tool can only do what your website already lets the visitor do, and your server still checks permissions. Good tools are small and specific, validate every input, and mark sensitive actions (booking, adding to cart, sending a form) so the browser or agent asks the visitor first. Chrome supports hints for this, such as readOnlyHint and consequentialHint. Never expose admin functions or other customers’ data through a tool.

What to do now

1. Check where you stand. Run your site through the free WebMCP checker. It lists any tools and checks the data agents would need.
2. Pick two or three actions. The questions customers ask most: search, details, availability, contact.
3. Start read-only. Tools that only look things up are the safest and most useful first step.
4. Add sensitive actions later, always with the visitor’s confirmation.

Running WordPress or WooCommerce? Read our step-by-step guide on how to add WebMCP to WordPress and WooCommerce, and our comparison of WebMCP and MCP servers. If you would rather have it done for you, our WordPress WebMCP integration service starts with a free readiness audit.