Give any website a WebMCP interface
- File:
raw/cloudflare-2026-webmcp.md - URL: https://blog.cloudflare.com/webmcp/
- Author: Will Rowe
- Date: 2026-08-06
- Type: primary vendor announcement
Summary
Cloudflare’s WebMCP developer preview can inject a same-origin bridge script at the edge, allowing supported browser agents to discover tools associated with a website without modifying the origin application. WebMCP appears experimentally in Chrome 146 as document.modelContext; sites register explicit tools so agents need not infer actions from visual navigation. Cloudflare’s BrowserRun can already discover and call those tools.
The preview organizes tools into opt-in packs. The initial Content Credentials pack reads C2PA metadata from images, while the Site MCP Server pack discovers tools from a site’s existing same-origin MCP endpoint and proxies calls using the visitor’s current session. The bridge runs in the browser; if WebMCP is unavailable it does nothing, preserving ordinary site behavior. Cloudflare notes that its C2PA tool decodes asserted provenance but does not cryptographically verify it, exposing signatureVerified: false so agents do not confuse a claim with a verification.
For the business, WebMCP is not a magic “make this site transactional” switch. Useful business actions still require a properly designed and secured MCP server or future tool pack. Its immediate relevance is as a low-friction delivery surface for one narrow conversion action after an Agent Readiness audit: for example, exposing search, availability, or a constrained appointment-request tool to browser agents. It also creates a measurable proof loop—enable the interface, use BrowserRun to discover/call it, and preserve the result. Because WebMCP and Cloudflare’s feature are developer previews, any client offer should describe them as experimental and keep a normal human interface and API path intact.
Key Claims
- Cloudflare can inject a WebMCP bridge without changing origin code.
- WebMCP is experimental in Chrome 146 and Cloudflare’s implementation is a developer preview.
- BrowserRun can discover and call registered WebMCP tools.
- Existing site MCP tools can be proxied through the visitor’s same-origin session.
- Initial packs are limited; meaningful business actions still need backend capability and security.
Connections
- Entity: Cloudflare
- Concepts: Agent-Callable Websites, Agent Readiness, Agentic Service Operations
Contradictions
- Refines the roundup: “give any website a WebMCP interface” does not mean Cloudflare automatically invents useful business tools for that website.