Cloudflare announced a developer preview that lets any website enable a WebMCP (Web Model Context Protocol) interface with a single dashboard switch. This allows browser-based AI agents to interact with unmodified web pages through structured tools instead of scraping or guessing, keeping human traffic and control on the original site.

The core idea behind WebMCP is exposing structured, machine-readable tools directly to AI agents through a standard protocol. This allows them to call explicit functions like searchFlights or bookTicket without resorting to scraping and parsing HTML, which consumes tokens, or clicking UI buttons to trigger behavior. WebMCP makes interactions faster, more efficient, and far less fragile than traditional browser automation, which often breaks when the UI changes.

To adopt WebMCP, a website must expose its functionality as tools using either the document.modelContext API, which allows developers to register tools, define their schemas, and write the code that implements them, or a declarative JavaScript API that allows to add annotations to a standard HTML forms to create a WebMCP tool.

What CloudFlare's current preview is aiming at is giving any site on Cloudflare the possibility to support WebMCP with a single switch by selecting tool packs from a pre-defined library. CloudFlare is currently including two tool packs in this preview: Content Credentials to allow agents to read C2PA content-provenance metadata from images on the page, and Site MCP server, which can proxy a site's MCP server tools to the in-browser agent. CloudFlare says the tool pack library will grow and that when new packs become available, a site can enable them without redeploying.

CloudFlare's implementation is built around a bridge.js module, which is silently injected into a served webpage using HTMLRewriter:

```

`` The module reference lists the tool packs adopted by the page in thedata-packsattribute along with any additional parameter required (e.g.,data-mcp-url` for the Site MCP server tool pack).

From there, the bridge composes the packs named in

data-packsinto one tool list and registers each with.registerTool. A pack is just a set of MCP tool descriptors and their handlers. Static packs, such as Content Credentials, declare their tools up front. A dynamic pack, such as the Site MCP Server pack, discovers its tools at boot before registering anything.

Existing MCP tools running on the server are discovered through the standard MCP Tool type, so for each of them the bridge registers a WebMCP proxy whose execute() method calls the site back on the same origin. Likewise, the bridge pass through a standard CallToolResult to handle the execution result.

CloudFlare WebMCP preview is highly work in progress. The WebMCP standard is itself a preview and only supported in Chrome 145+. You can enable WebMCP by going to Agent Readiness > Labs in the Cloudflare Dashboard, toggle on WebMCP for your domain, and select the desired tool packs.