Daniel Rosehill

The Shift That's Coming

Today, if an AI agent wants to interact with your website, it has to do what a human would do: load the page, look at it, figure out where the buttons are, and click them. This works — sort of — but it's slow, fragile, and entirely dependent on visual layout staying consistent.

WebMCP changes the model. Instead of agents interpreting your UI visually, your site declares what actions are available through structured tool definitions. The agent calls these tools directly with typed parameters and gets structured data back. No screenshots, no DOM parsing, no guessing.

Chrome opened an early preview of WebMCP in February 2026 and an origin trial from Chrome 149, which lets sites switch it on for real visitors. The specification is still a community-group draft, edited by Google and Microsoft engineers, and it isn't in stable Chrome by default yet — but the trajectory is clear: the browser is becoming an MCP client, and websites need to become MCP servers.

Why E-Commerce Operators Should Care First

If you run an online store, this is your problem before it's anyone else's. Here's why:

  • Agent-mediated shopping is growing. Consumers are already asking AI assistants to find products, compare prices, and even complete purchases. The agent needs to interact with your site to do this.
  • Visual scraping puts you at a disadvantage. When an agent scrapes your site visually, it's working with lossy, unstructured data. Prices might be misread, availability might be stale, product variants might be missed. Your competitor with structured tools gets the accurate result.
  • You lose control of the narrative. A scraping agent decides what information matters. A WebMCP implementation lets you define exactly what data and actions are available — and how they're described.
  • Checkout conversion depends on it. An agent that can call add_to_cart and checkout as structured tools will complete purchases. An agent that has to visually navigate a checkout flow will abandon it at the first unexpected modal.

A Readiness Checklist

You don't need to wait for WebMCP to hit stable Chrome to start preparing. Most of the groundwork is architectural, and it pays off regardless of the specific protocol timeline.

1. Audit Your Core User Flows

Map every action a customer takes on your site: search, filter, view product, select variant, add to cart, apply coupon, checkout. Each of these will become a tool definition. If you can't describe the action as a function with typed inputs and outputs, the flow needs simplification.

2. Separate Your Data Layer from Your Presentation

If your product data only exists as rendered HTML, you have a problem. WebMCP tools need to return structured data — JSON, not DOM fragments. This usually means ensuring you have a clean API or data access layer behind your frontend. If you're already running a headless commerce setup, you're ahead.

3. Define Your Tool Surface

Draft the tool definitions you'd want to expose. Start with the high-value actions:

  • search_products — query, filters, sort, pagination
  • get_product_details — full product data including variants, pricing, availability
  • check_availability — real-time stock for a specific SKU and location
  • add_to_cart — product ID, quantity, variant selections
  • get_cart — current cart contents with pricing
  • apply_promotion — coupon or discount code validation
  • initiate_checkout — begin the purchase flow

You can register these as WebMCP tools today under the origin trial, but you don't have to. Having the definitions ready means you can move quickly whenever you choose to — and they are useful for a backend MCP server in any case.

4. Clean Up Your Forms

Chrome has said HTML forms can be exposed to agents as tools. If your forms are well-structured — proper labels, typed inputs, clear action attributes — they'll map to tool definitions more naturally. If your forms are a mess of hidden fields and JavaScript overrides, now is the time to clean them up.

5. Invest in Structured Data

Schema.org markup, JSON-LD product data, OpenGraph tags — all of this helps agents understand your content even before WebMCP is available. Sites with rich structured data will have an easier transition to WebMCP's structured tool model.

6. Consider Your Auth Model

Some WebMCP tools will require authentication — personalised pricing, saved carts, account-specific promotions. Think about how agent authentication will work alongside your existing user auth. OAuth 2.1 flows that can be initiated by an agent on behalf of a user are the likely pattern.

The Broader Preparedness Picture

WebMCP is one piece of a larger trend: the web is becoming a surface for AI agents, not just human browsers. Preparing for WebMCP is really about preparing for the agentic web — a world where a significant portion of your site's "visitors" are AI agents acting on behalf of humans.

Think of It as Agent-SEO

Just as SEO made your content discoverable to search engines, WebMCP preparedness makes your services accessible to AI agents. The businesses that optimise for agent interaction will capture the growing share of commerce that flows through AI assistants.

What Not to Do

A few anti-patterns to avoid:

  • Don't build a separate "agent version" of your site. WebMCP is a layer on top of your existing site, not a parallel implementation. Your tools should call the same APIs your frontend does.
  • Don't wait for the final spec. The architectural work — clean data layers, well-defined user flows, structured data — is valuable regardless of protocol details.
  • Don't try to block agents. The retailers who tried to block search engine crawlers in the early 2000s learned this lesson the hard way. Agent traffic is customer traffic.
  • Don't expose everything. You control your tool surface. Expose the actions that benefit your business and your customers. Not every internal endpoint needs to be an agent-callable tool.

The Timeline

Where things stand in October 2026:

  • February 2026: Early preview in Chrome behind a flag, for developer feedback
  • From Chrome 149: Origin trial — sites can enable WebMCP for real visitors with a trial token. Google said at I/O in May 2026 that Gemini in Chrome will soon support it
  • Next: Stable availability depends on the trial and on the specification maturing — it is still a draft, and the API has already changed shape once

The architectural work pays off now regardless of timing. The WebMCP-specific layer is thin by comparison — this site registers its read-only tools in a single script — and can follow as the protocol settles.