Cloudflare's Kitesurf browser now speaks WebMCP to agents

Cloudflare introduced Kitesurf in August as a browser for the agentic age that runs entirely on Workers, built around what agents need from the web rather than what a person needs from a window. The company's 28 September update is the first substantial report card on that idea, and it concentrates on three things: letting websites hand agents proper tools, widening the set of web standards the engine can actually render, and shaving the latency out of the loop an agent runs every time it looks at a page.

WebMCP turns a site into a set of callable tools

The headline addition is support for WebMCP. Rather than clicking pixels and hoping the right element loads, an agent can discover and call functions a site has exposed, which is the difference between a script that survives a redesign and one that breaks on a Tuesday. Cloudflare says site owners can already switch WebMCP on without changing their code, and that Kitesurf now consumes it. You can watch the browser exercise those tools on Cloudflare Radar: point the DevTools panel at the Application tab, open Radar and the exposed tools are listed there.

Targeting Kitesurf from your own agent is a websocket connection to Browser Run: wss://api.cloudflare.com/client/v4/accounts/<ACCOUNT_ID>/browser-run/devtools/browser?browser=kitesurf

More standards, and a faster loop

The engine now covers more of the browser surface, including the streaming and chunk-loading behaviour that decides whether a modern site renders at all. Iframes load at the right moment, stay better isolated and render text correctly across more languages and encodings. Cloudflare measures the progress against the Web Platform Tests, the shared open-source suite that checks whether browsers implement standards consistently, and says coverage has grown by 500,000 subtests since launch.

For an agent, speed is less about how quickly a page paints and more about how long each decision takes. Cloudflare has reworked the boundary between its Wasm DOM and JavaScript engines so common reads are answered inside the Wasm DOM instead of making repeated round trips, released memory from objects it no longer needs, and made font handling lazier: fewer unused fonts fetched, language-specific files pulled only when the right characters appear on the page, and synthetic italics rendered more faithfully. Despite the broader standards support, the company says wall-clock time and CPU usage are roughly in line with the launch benchmarks, and in some cases better.

Full Browser Run coverage and a terminal renderer

Kitesurf now has full Browser Run API coverage, so the same Quick Actions that capture screenshots, extract HTML and generate PDFs from the REST API can be called from inside a Worker script. Cloudflare has also leaned on the split between PageScript, which runs the page session, and PageRenderer, which turns computed page objects into pixels. Because rendering can be moved outside Kitesurf while the security-critical code stays on Cloudflare's network, the team wired PageRenderer to output the Kitty terminal graphics protocol, with a plain ANSI text mode as a fallback. You can now open and scroll a page, and see what an agent sees, without leaving the terminal.

Our opinion

The terminal renderer looks like a party trick and is arguably the most useful thing in the post. Agent debugging is miserable precisely because the agent's view of the page is invisible; being able to render that view in the same window as the logs is the kind of tooling that saves an afternoon. WebMCP is the more consequential bet, though, because it asks website owners to publish their functionality for machines. Every site that does it makes agent browsing less brittle, and every site that refuses keeps agents guessing at pixels.

The obvious gap is still the licence. Cloudflare has promised to open-source Kitesurf for months and the post repeats that it is coming soon, which means anyone building on it today is trusting a roadmap. There is a commercial logic to that: WebMCP plus Browser Run plus Workers is a tidy way to sell the plumbing that makes agents work, and an open-source browser that only runs on your own platform is a subtle kind of lock-in. Renting an agentic browser is fine for a prototype, but teams that have been burned by a vendor changing terms should watch for the licence before they move a production pipeline across.