WebMCP
Last updated
Most AI search discussion focuses on content: what a page says, how it is structured, whether an AI system can retrieve and cite it. WebMCP operates at a different layer. It is not about what a page contains but about what can be done on it. It is the protocol that makes a website callable by an AI agent, not just readable.
WebMCP (Web Model Context Protocol) is a proposed web standard in early preview as of February 2026. It was developed through the W3C Community Group with Google and Microsoft as co-developers, and is available in Chrome 146 Canary behind the “WebMCP for testing” flag.1
What is WebMCP?
MCP (Model Context Protocol) was introduced by Anthropic in late 2024 as a standard for connecting AI models to external tools and data sources. It has since been adopted broadly across the AI industry. WebMCP is an adaptation of that protocol for the browser: a way for a website to declare its own callable tools in a format that a browser’s in-built AI agent can discover and invoke.
Where a conventional web page communicates with users through HTML that humans read and navigate, a WebMCP-enabled page also communicates with AI agents through structured tool definitions that machines can call directly via the navigator.modelContext JavaScript API.
WebMCP introduces two APIs:
- Declarative API: standard actions defined directly in HTML forms; the agent interprets and calls them without JavaScript execution
- Imperative API: dynamic interactions requiring JavaScript, for complex or stateful operations
WebMCP is not a crawler-facing protocol. It does not affect how search engines index a page. It operates at the browser and agent layer, at the moment a user’s AI agent takes action on their behalf.
How does WebMCP differ from structured data?
Structured data and WebMCP address different questions. Structured data says what a page contains. WebMCP says what can be done on it.
| Structured data | WebMCP | |
|---|---|---|
| Question answered | What does this page contain? | What can be done on this page? |
| Consumed by | Search crawlers, indexing systems | In-browser AI agents at action time |
| Format | JSON-LD / schema markup | Structured tool definitions at a known endpoint |
| Example | This is a Product with a price of £49 | Here is a checkAvailability function |
The two are complementary. Structured data improves how AI systems understand and index content. WebMCP enables AI agents to act on content on behalf of users. A site implementing both gives AI agents both the context to understand what they are looking at and the tools to take action on it.
How does WebMCP differ from agentic SEO?
Agentic SEO is about the content retrieval layer: structuring pages so that AI research agents can find, read, and synthesise relevant passages across a multi-step task. The agent browses, reads, and reports.
WebMCP is about the action layer: declaring what an agent can do on a site once it gets there. Instead of simulating user behaviour (navigating to a search box, typing a query, scrolling through results), an agent calls a searchProducts function and receives structured JSON back in a single operation.
A site without WebMCP can still be cited and retrieved by agents. WebMCP determines whether agents can also act on a site’s behalf, which is a different capability entirely.
Which sites should implement WebMCP?
The value of WebMCP scales with how much of a site’s utility involves completing tasks rather than reading information.
High priority now:
- E-commerce:
searchProducts,checkAvailability,addToCart,trackOrderare the obvious candidates. An agent shopping for a user needs to query inventory, check delivery options, and initiate a purchase. Without WebMCP this requires simulating dozens of browser interactions; with it, a few structured calls. - Travel and booking:
checkDates,searchFlights,bookAppointment,cancelReservation. Agentic travel research is already a primary use case for tools like Gemini Spark. - Local services:
requestQuote,checkAvailability,bookService. Google’s agentic booking feature (announced at I/O 2026) handles calls to businesses for home services, beauty, and similar categories, though this runs on Google’s own infrastructure rather than WebMCP directly.2 - SaaS and tools: any site where the primary action is doing something in a logged-in context: creating a document, running a report, triggering a workflow.
Lower priority for now:
Editorial and informational sites. Agents read and synthesise this content but do not act on it. The relevant investment for these sites remains content quality and retrieval optimisation, not WebMCP implementation.
Current state and timeline
WebMCP has been available in Chrome 146 Canary behind the “WebMCP for testing” flag at chrome://flags since 10 February 2026. It is in early preview for developers, not a feature available to general users.
The W3C Community Group formally accepted the spec in September 2025. Google and Microsoft are co-developers. Full Chrome and Edge stable support is expected mid-to-late 2026, pending the standard maturing and adoption increasing.
Gemini Spark, Google’s personal AI agent announced at I/O 2026, integrates with MCP out of the box for Google’s own tools, with third-party tools following weeks after launch.2 This signals the direction: MCP (and by extension WebMCP) is becoming the expected interface between AI agents and the services they use.
The spec may evolve before stable release. Treat current implementations as experimental.
The agent protocol stack
WebMCP is one layer in a broader stack of agent protocols. Each addresses a different coordination problem.
MCP (Model Context Protocol): the open standard developed by Anthropic and now adopted across the AI industry, including by Google and Microsoft. MCP defines how AI models connect to external tools and data sources. An MCP server built for one platform works with any MCP-compatible agent. Gemini Spark ships with MCP support at launch, with 30+ third-party integrations available at or near release.2
WebMCP: the browser-native adaptation of MCP covered in this article. Where standard MCP connects server-to-server, WebMCP exposes callable tools directly in the browser via the navigator.modelContext API, at the moment a user’s in-browser agent takes action.
A2A (Agent-to-Agent Protocol): a Google-developed open standard for coordination between agents. When one agent delegates a sub-task to another (for example, Gemini Spark handing a specialised research task to a retrieval agent), A2A manages the handoff, authentication, and result passing. Adopted by more than 150 organisations including Microsoft, AWS, Salesforce, and SAP.3 Publishers do not implement A2A directly; it operates at the infrastructure layer and explains how multi-agent chains resolve across different systems.
UCP (Universal Checkout Protocol): Shopify’s commerce-layer protocol for agent-initiated transactions. UCP exposes checkout endpoints that AI shopping agents can invoke directly to complete a purchase, rather than navigating a standard checkout flow. Covered in the planned e-commerce SEO pillar.
For most informational and editorial sites, MCP and WebMCP are the relevant layers: they cover what your site can offer agents that interact with it. A2A operates between agents and is not publisher-facing. UCP applies to commerce sites managing agent-initiated transactions.
What to do now
Informational and editorial sites: no implementation needed. Monitor adoption as the spec matures. The primary investment remains structured data and content quality for retrieval.
E-commerce, travel, booking, and service sites: worth prototyping now. Review the Chrome for Developers WebMCP documentation and identify two or three high-value actions that would most benefit from agent invocation. Early implementers will have a lead as browser support reaches general users.
All sites: ensure existing structured data is solid. Structured data remains the primary signal for content understanding and indexing. WebMCP supplements it; it does not replace it. A site with strong schema markup and weak WebMCP support is better positioned than the reverse.
Frequently asked questions
Does WebMCP affect search rankings?
No confirmed mechanism exists by which implementing WebMCP improves search rankings or AI citation rates. WebMCP operates at the action layer, not the indexing or retrieval layer. It has no known effect on how Google’s search systems rank or cite content.
Is WebMCP the same as MCP?
Related but distinct. MCP (Model Context Protocol) is the broader Anthropic-developed standard for connecting AI models to external tools and data sources. WebMCP is a browser-native adaptation of that protocol, letting websites expose tools directly to in-browser AI agents via the navigator.modelContext API. WebMCP uses MCP’s tool definition format but operates in a browser context rather than a server-to-server one.4
Do I need WebMCP to appear in AI search answers?
No. Appearing in AI-generated answers is a retrieval and content quality question, covered by agentic SEO and GEO principles. WebMCP is about agent actions, not agent citations.
Will Google’s agentic booking feature use WebMCP?
Google’s agentic booking (placing calls to businesses on a user’s behalf) uses Google’s own infrastructure and is not directly tied to WebMCP. The two are complementary in intent but separate in implementation. WebMCP provides a standardised open protocol; Google’s agentic booking is a proprietary feature that may or may not adopt WebMCP as the standard matures.