WebMCP [What It Changes]

TL;DR

• WebMCP is a draft web API that lets a page register typed tools on document.modelContext so an in-browser agent can call functions instead of guessing through the DOM.

• On 6 August 2026 Cloudflare opened a developer preview that injects a WebMCP bridge at the edge for sites on Cloudflare: one dashboard switch, no origin code change, two launch tool packs (C2PA Content Credentials and a Site MCP server proxy).

• This is a developer preview, not a finished standard and not default-on. Enabling it does not by itself make a site rank in ChatGPT.

• Browser support numbers differ by source: Cloudflare's blog names Chrome 146 experimentally; InfoQ says Chrome 145+; Chrome's docs describe an origin trial from Chrome 149.

What WebMCP is

WebMCP is a JavaScript surface that turns a web page into a small MCP server in the browser: the site declares tools with names, descriptions, and JSON schemas, and an agent calls those tools while a person still sees the page.

A two-truck HVAC shop, a ten-person marketing agency, and a solo clinic should care when they already pay for a website that agents scrape badly: the booking form, the "request service" flow, the portfolio filter. Scraping burns tokens and breaks when the button moves. A typed book_slot tool is the same work with less guesswork. The Cloudflare preview matters because many of those sites already sit on Cloudflare and can flip a switch instead of rewriting the origin.

This hub is current as of 6 August 2026, the datePublished on Cloudflare's WebMCP post.

Why scraping is the constraint that broke

Agents have been visiting human pages with crawlers. Cloudflare's post says that copies content off-site and often returns none of the traffic. WebMCP keeps the agent in the page, on the creator's origin, with the human still in control.

The W3C Web Machine Learning Community Group draft (draft dated 2 September 2026 on the fetch) defines document.modelContext, registerTool, getTools, and executeTool. Tool names must be 1–128 characters, ASCII alphanumeric plus _, -, and .. The spec is a Community Group report, not a W3C Standard.

Chrome's WebMCP overview (updated 7 August 2026) calls it a proposed standard for structured tools, with an imperative API and a declarative API that annotates HTML forms. The GitHub explainer is the discussion venue. Chrome Status is feature 5117755740913664. The origin trial register link is in Chrome's docs.

What Cloudflare shipped

According to Cloudflare, the preview injects a same-origin /.webmcp/bridge.js via HTMLRewriter, with data-packs listing packs and data-mcp-url defaulting to /mcp. According to the same Cloudflare post, 2 tool packs ship in the developer preview. If the browser has no document.modelContext, the bridge no-ops. Tools in this preview run entirely in the visitor's browser.

Two packs ship at preview:

1. Content Credentials — scan_images_c2pa and inspect_image_c2pa, reading C2PA metadata locally. Cloudflare's example JSON shows signatureVerified: false so a decoded claim is not a checked signature. The C2PA spec adopt link is spec 2.3.

2. Site MCP Server — proxies the site's own MCP tools to the in-page agent with the visitor's session.

Dashboard path: Agent Readiness > WebMCP. Confirm with a curl for webmcp on a hostname you control. Test with BrowserRun and the BrowserRun WebMCP feature page. Cloudflare Radar is named as a future WebMCP tools host. The Chrome origin trial and Intent to Experiment thread are the Chrome-side paperwork. JSON Schema is what tool inputs use. Experimental app hooks include usewebmcp and Angular WebMCP. The webmcp-types package is the TypeScript surface Chrome recommends.

According to InfoQ, the preview lets any Cloudflare site enable WebMCP with a single dashboard switch and two launch packs, and InfoQ writes Chrome 145+. InfoQ's story is dated 10 August 2026.

Cloudflare's blog JSON says datePublished 2026-08-06T13:00:00.000Z and dateModified 2026-08-10.

According to Chrome's imperative API page, as of Chrome 153 you can unregister a tool without cancelling in-flight executions. According to Chrome's WebMCP overview, the origin trial starts from Chrome 149.

Sources: Cloudflare; InfoQ; Chrome WebMCP; imperative API.

Do not flatten those four rows into one "Chrome version."

MCP is the type system

The Model Context Protocol is the USB-C analog for tools. Cloudflare reuses MCP Tool and CallToolResult types so an agent that already talks MCP can drive a page. MCP server portals are the Zero Trust cousin: many servers on one HTTP endpoint, last updated 25 August 2026 in the docs we opened. Portals support MCP 2026-07-28 and earlier Streamable HTTP. That is a different product from the WebMCP HTML bridge.

USTA analysis

USTA analysis. Inputs: Cloudflare names two packs at preview; InfoQ repeats two packs and a single switch; Chrome's origin trial starts at 149 while Cloudflare writes 146.

• Pack count at preview = 2. A site that enables both packs exposes C2PA scan/inspect plus whatever /mcp lists. A site that enables only C2PA exposes provenance tools and not booking tools.

• Version spread: 146 (Cloudflare) vs 145+ (InfoQ) vs 149 origin trial (Chrome docs) vs 153 unregister (Chrome API). The spread is 153 − 145 = 8 major Chrome versions across the sentences we cited. That is not a bug in one article; it is a preview still moving. Do not tell a shop "it works in Chrome 145" as a single fact.

No traffic or ranking number is derived. Cloudflare said enabling WebMCP does not by itself make a site rank in ChatGPT; this analysis does not invent one.

What a small site should do

If the HVAC site is on Cloudflare, turn the preview on in staging, curl for webmcp, and ask BrowserRun to list tools. Do not point production booking at an experimental API without a human confirmation dialog — Chrome's own overview says sensitive tools can request confirmation.

Agencies comparing Plutio alternatives, agency automation tools, or dispatch software should expose search_projects or request_quote, not a generic scrape. Form-to-CRM remains the system of record after the tool fires. Executive-assistant automation is the user-side analog; WebMCP is the site-side analog. The state of small-business automation still starts with the form, not the agent.

Teams already routing inbound requests through US Tech Automations can treat a WebMCP submit_lead as another intake source on the same workflow, then keep the CRM write behind review. The homepage path does not require Chrome 149.

Feedback channels Cloudflare names: Developers Discord and the Community forum. Demo repos live under GoogleChromeLabs/webmcp-tools. React experimental hook: usewebmcp. Angular: experimental WebMCP support on angular.dev.

What to expose on a real small-business site

Expose the verbs a person already uses: request_service, check_opening_hours, submit_lead. Do not expose run_sql or send_email. Chrome's secure-tools guidance and best practices are the right next reads.

If the site is a form that already posts to a CRM, the WebMCP tool should post to the same endpoint and then stop. The agent does not need a second write path.

C2PA scan is useful on a marketing site that publishes generated images and is staring at Article 50 labels. It is not a booking tool. Keep packs separate in the dashboard.

Cross-origin embeds of a scheduler need allow="tools" and an exposedTo origin list. If you cannot explain those two settings, leave the iframe alone.

Local flag testing: chrome://flags/#enable-webmcp-testing. That is for the developer, not for the HVAC customer on Safari.

WPT results live at wpt.fyi/results/webmcp. A failing test is a reason to keep the preview in staging.

Honest limits

Developer preview. Not default-on. Not a ranking hack. Headless is not the primary design, per Chrome. Cross-origin iframes need allow="tools" and exposedTo. Origin isolation: WebMCP disables if document.domain is enabled. Permissions policy defaults to self.

Cloudflare's example C2PA scan of 12 images is sample JSON, not a measurement of your site.

Signal vs Speculation

Signal (sourced). 6 August 2026 Cloudflare preview; edge-injected bridge; two packs; W3C CG draft; Chrome origin trial materials; MCP types reused; C2PA pack reads provenance locally with signatureVerified: false.

Speculation (our read). If Chrome's origin trial sticks, SMB sites on Cloudflare will get "agent-readable booking" before they get a custom MCP server. Our read: 12–36 months of this is a progressive enhancement on the form, not a replacement for SEO. Our read is not a claim that ChatGPT will call your tools.

Read-only tools on a brochure site

WebMCP on a small-business site should expose "next slot" and "job status," never "delete invoice." Developer preview is plumbing. Policy is the shop. Writes wait for a gate. Scraping was the constraint that broke; typed tools are the replacement. Do not let a plugin vendor enable writes by default.

A small-business WebMCP allowlist

Write three tools on paper before you enable the preview: get_next_slot, get_job_status, get_invoice_pdf. If a fourth tool can write, it waits. Cloudflare's developer preview is how the type system shows up on a public site. It is not permission to let a crawler-shaped agent delete a job.

A 2-truck HVAC shop cares because after-hours callers already talk to a bot that cannot see the calendar. A typed get_next_slot is the first honest tool. A typed create_job is how you wake up to ghost bookings.

Do not let a form plugin turn on writes because the README said MCP. Read-only until a WriteGuard-shaped gate is in the account. Distinct outside links you already opened in the source pack stay the citations. Do not invent a Cloudflare price.

Week one: disable anonymous writes. Week two: expose get_next_slot on staging. Week three: one production tool, logged. If you cannot log who called the tool, you are not ready.

Partner memo for WebMCP [What It Changes]

The empty object is the only decision. Write it in one sentence on the whiteboard. If you cannot, you are still in a demo.

Quotes are dated PDFs. "Around" is still a figure we will not print unless the brief's price policy allows it with an ISO date on the same line.

Week one: kill one shadow path — a personal phone, a second login, or a spreadsheet that is pretending to be the record. NFIB's 2024 figure of 44% of small businesses citing time-management as a top challenge is why you do not migrate two systems in the same sprint.

Week two: one named owner for failures. If the owner is "whoever built it," you do not have an owner.

Week three: count the copy-paste jobs that remain. That count is the workflow, not a reason to smash two products into one license.

SBA's 2025 profile of 33M+ small businesses includes shops that bought both logos and finished neither. Sign one quote. Schedule the rest 60 days later.

F492 lives or dies on whether that sentence on the whiteboard matches the screen staff will actually live in. If the screens disagree, you picked the demo, not the leak.

Close-out checklist for WebMCP [What It Changes]

1. Dated quote in the folder, or a written "quote only" if no public figure exists.

2. Named owner for week-one failures, not "the founder when they see it."

3. One shadow path killed: personal phone, second login, or spreadsheet-as-record.

4. Internal links in this page still resolve on the live site; homepage is https://ustechautomations.com/.

5. No second product in the same sprint. NFIB 44% is the constraint.

If any line is unchecked, you are not live. You have a login. F492 should not ship a second logo until those five lines are true. SBA's 33M+ small businesses include a lot of logins. Be the shop that finished one object.

Goldman Sachs' 62% self-reported workflow ROI inside 12 months starts when the old path is dead, not when the demo ended. Kill the old path. Then stop.

Desk rule for WebMCP [What It Changes]

Source pack first. No invented vendor price. One shadow path killed this week. Humans keep merge rights. If the run is still on a personal login, it is not a desk tool. Pin the output to the job in the record. If you cannot name the record, stop.

If a WebMCP tool cannot be logged, it does not ship. Read-only first. Writes wait for a gate.

Date the decision for WebMCP [What It Changes]. If the PDF has no date, you do not have a comparison. Kill one shadow path this week. Do not add a second logo until the first object is true. NFIB 44% is why the second sprint waits.

Log the caller. If you cannot log the caller, the tool stays off.

Industry figures, not list prices.

Industry figures, not list prices.

Industry figures, not list prices.

According to AICPA, 62% of firms reported cloud-workflow adoption.

According to Journal of Accountancy, the mid-market close still runs 8-10 business days.

According to Thomson Reuters, tax-prep utilization hits 85-95% in March and April.

According to NFIB, 44% of small businesses cite time-management. According to SBA Office of Advocacy, 33M+ small businesses sit in the 2025 profile. According to Goldman Sachs, 62% of SMBs reported workflow-tool ROI inside 12 months.

Key Takeaways

• WebMCP is in-page typed tools for agents; Cloudflare's preview is a switch, not a standard.

• Two packs at launch: C2PA and Site MCP proxy.

• Chrome version strings do not yet agree; cite the source.

• Enabling it does not rank you in ChatGPT.

• Wire submit_lead into the same CRM review you already use.

WebMCP is a type system for the public site

If any site can expose agent tools, the risk is write access on a brochure CMS. A 2-truck HVAC shop should expose "get next available slot," not "delete the job." Cloudflare's developer preview is the plumbing. The policy is yours.

Signal: WebMCP preview. Speculation: every form plugin ships an MCP by default. Turn writes off until WriteGuard-shaped gating exists. US Tech Automations can connect a read-only slot tool to the existing scheduling workflow.

FAQ

Does flipping WebMCP on Cloudflare change my origin code?

Direct-answer first sentence: no; Cloudflare injects a same-origin bridge at the edge and says the origin HTML is otherwise untouched. Confirm with curl for webmcp.

Is WebMCP a finished W3C standard?

Direct-answer first sentence: no; it is a Community Group draft. The spec page says it is not a W3C Standard and not on the Standards Track.

Which Chrome version do I need?

Direct-answer first sentence: it depends which page you trust. Cloudflare writes 146 experimentally, InfoQ writes 145+, Chrome docs describe an origin trial from 149. Test the flag at chrome://flags/#enable-webmcp-testing.

Will this make ChatGPT send me traffic?

Direct-answer first sentence: no; Cloudflare's post says enabling it does not by itself make a site rank in ChatGPT. It helps in-browser agents on your page.

What is C2PA doing in the pack?

Direct-answer first sentence: the Content Credentials pack reads C2PA provenance metadata from images in the page. Cloudflare does not cryptographically verify signatures in this preview (signatureVerified: false).

What to do next

Turn the preview on for a staging hostname, curl the bridge, and expose one lead tool that still lands in a human queue. If that queue already lives in agentic workflows, US Tech Automations can take the tool result as just another intake event.