Your Website Just Got a Second User Interface

What actually shipped, and who says so#

The fox has watched this burrow for a while. When we rebuilt our own site's agent layer earlier this year, the WebMCP spec had already churned once under our feet, so the question of who actually consumes it has been a live one in this den for months. As of this week there is a clean answer: ChatGPT. Search Engine Journal reported on 27 August that OpenAI's desktop browser now supports site tools, and OpenAI's own documentation confirms the shape: site tools are ChatGPT's implementation of the proposed WebMCP standard, letting sites offer useful actions directly to an AI agent alongside the interface people already use.

The scope notes matter as much as the headline. Site tools work in the ChatGPT desktop app's built-in browser, in ChatGPT Work and in Codex, on the GPT-5.6 Sol and Terra models, with Luna excluded, and they are not available in Enterprise or Edu workspaces. Tools must be registered by the top-level page: anything inside an iframe is not discovered. Every invocation gets a safety review, and consequential actions, the docs name sending messages, purchases, deletions and permission changes, still require user confirmation.

OpenAI is also paying to seed the field. Its WebMCP Challenge, posted from the company's own Reddit account, offers $35,000 in prizes for apps people and their agents use together, with Google Chrome, Cloudflare, Shopify, Vercel, Render and Netlify as supporters and a 3 September deadline. Platforms do not co-sponsor hackathons for standards they intend to let die.

So what is webmcp, underneath the demo?#

Anyone asking what is webmcp gets a tidy answer from the specification itself. It is a proposal incubated in the W3C Web Machine Learning Community Group: a JavaScript API on the document, where a page calls document.modelContext.registerTool with a name, a description, an input schema and an execute handler. There are companions for listing and calling tools and a toolchange event, but registerTool is the load-bearing beam. Feature detection is one line, and a page without an agent visitor pays nothing.

The name is honest about its parentage. The model context protocol, the standard Anthropic introduced for wiring AI models to external tools, supplied the mental model; WebMCP moves the same idea into the page itself, and the agentic web starts looking like a place rather than a metaphor. The distinction from a conventional backend MCP server is worth keeping crisp, because the two will coexist on many estates.

OpenAI's docs put the shared-context case plainly: site tools shine when you and the agent need to see the same thing, such as editing a canvas or exploring a dashboard. That is the genuinely new territory. A backend integration cannot know what is on the user's screen; a site tool is standing in the same room.

Where the other browsers stand#

Per the community group's own implementation status page, an origin trial is live in Chrome 149 and another in Edge 150, Brave has experimental support in its Leo assistant, and Firefox and Safari sit at the standards-position stage. ChatGPT Desktop is listed as supported outright. For a proposal this young, that is an unusually crowded field of foxes circling the same henhouse.

The traffic reality that makes this urgent#

None of this would matter commercially if agents were a novelty audience. Cloudflare's measured numbers say otherwise, and they are worth quoting precisely because they come from the network layer rather than a vendor deck. Its agentic internet report of 1 July 2026 finds more than half of internet traffic is now non-human, that 52% of crawler requests are for AI training as of June 2026, up from 22% in spring 2025, and that some heavily crawled content categories have watched human traffic fall by as much as 40% in under a year.

Read that slope with a marketer's eye and the shape of the bargain is stark: machines take more and send less, and the fetches that represent a live human asking for something remain a sliver. The same Cloudflare research measured the crawl-to-referral exchange rate per platform, and it is brutal reading for anyone still pricing content on the click economy: by July 2025, Anthropic's crawlers fetched around 38,000 pages per referral sent, OpenAI's around 1,100, Google's under six.

That is the terrain the agentic web grows in. The visitor you are optimising for increasingly arrives as software wearing a person's intent, whether that is a chatgpt agent running an errand from the desktop app or a research assistant compiling options. OpenAI's own scale statement, more than 900 million weekly ChatGPT users as of February, says how much intent that software can carry. WebMCP is the first standards-track answer to the obvious question: if the agent is coming anyway, would you rather it guessed at your interface, or used the one you built for it?

Chrome is instrumenting the same shift from its side of the glass: Lighthouse now carries an experimental agentic browsing audit category, which checks pages for machine-readable affordances. An audit category is not a ranking signal, and Google says as much elsewhere, but it tells you which direction the browser vendors are pointing their headlights.

What builders hit when they actually ship it#

Between the specification and the demo sits the part nobody documents: the ditch. One WordPress developer spent launch week in it, wiring WebMCP tools into a live site, and surfaced with the kind of field notes that save everyone else a fortnight.

Every line of that is a lesson, but the last one is the strategy. Agent browsers budget how many tools a page may register, and a page that dumps its whole capability surface into the context gets silently cut. Curation is not optional. The page must offer the six tools that matter to a visiting chatgpt agent, not the 296 that exist, which is an editorial judgement before it is an engineering one. The fox does not carry the whole forest to the den; it carries tonight's dinner.

Our own scar tissue points the same way. When folkfox migrated its agent layer this spring, the original integration had been dead code for months because the spec had moved underneath it, from a navigator-level API to the document-level one ChatGPT now consumes. The maintenance model for this layer is closer to a living integration than a meta tag: versioned, feature-detected, and checked against the consuming agents each quarter.

The security posture to copy#

OpenAI's design treats every site-provided tool as untrusted, reviews each invocation, and gates consequential actions behind the user. Mirror that humility from the site side: expose read and stage actions freely, keep destructive ones behind your own confirmation steps, and never assume the agent's safety layer replaces yours. Chrome's team has been explicit that malicious tool descriptions and prompt injection are live risks for browser agents, which is exactly why the well-behaved site that describes its tools honestly will be the one agents' platforms learn to trust.

The AEO angle: what to do before September#

Here is the honest framing for marketing teams, and it cuts against the hype cycle. Site tools are a conversion-path play, not a rankings play. Nothing in OpenAI's documentation says WebMCP affects how often ChatGPT cites you, and nothing in Google's guidance ties it to rankings; the SEJ piece is admirably blunt that discoverability effects are simply not documented. Anyone selling WebMCP as the new SEO is selling the coat, not the mechanism.

What it actually changes is what happens after you are found. A chatgpt agent that lands on a competitor's page must screen-scrape its way to an enquiry; one that lands on yours can call request_quote with a structured payload. In a world where measurement of AI search traffic is already contested, a tool call is also a beautifully unambiguous analytics event: you will know precisely when an agent used the side door, which is more than most sites can say about their AI referrals today. Cloudflare's measured reporting will tell you how much agent traffic exists on the internet; only your own tool-call log will tell you what it did on your site. Our SEO and GEO practice treats this as the third layer of answer-engine work: be found, be quotable, and now be operable, and the citation-volatility lesson from earlier this month is precisely why the operable layer, which you control, beats chasing the quoted one, which you do not.

Prioritise by transaction shape. Catalogue businesses, booking flows, quoting tools and dashboards gain most; a brochure site gains little beyond a contact tool. Sequence it soberly: a small, curated tool set on one high-intent flow, feature-detected so nothing breaks for the 900 million humans, measured from day one. That is an afternoon of engineering on most stacks, not a replatform, and it is the same be-useful-to-the-machine discipline behind our content marketing services and app marketing work.

The patient prowl here beats the pounce. WebMCP is young, its spec has already shifted once, and only one agent platform consumes it at scale today. But the direction has stopped being ambiguous: the agentic web is becoming a place where humans and their software work side by side, and the sites that describe themselves honestly to both audiences will quietly outfox the ones still hoping the agent guesses right.

Frequently asked questions#