Cloudflare said on September 28, 2026 that Kitesurf, the browser for AI agents it introduced in August and which runs entirely on Cloudflare Workers, now supports WebMCP, covers the full Browser Run API surface and can render pages directly inside a terminal.
What changed
Cloudflare said Kitesurf now supports WebMCP, a mechanism the company describes as letting developers expose site functionality directly to agents so they can call functions such as searchFlights() instead of simulating clicks.
The company said users can test this in its public Kitesurf playground by opening Cloudflare Radar and navigating to WebMCP on the Application tab of the DevTools panel, where Radar exposes tools like navigate-to or set-location. Cloudflare said it has supported WebMCP since its early days and announced a few weeks ago that site owners can turn WebMCP on with one switch without changing their site's code.
Cloudflare also said Kitesurf now has full Browser Run API coverage and can be driven via CDP, Playwright, Puppeteer or MCP. Its Quick Actions feature, previously usable from the REST API, can now also be called from inside a Worker script using the env.BROWSER.quickAction() binding.
Standards coverage and performance claims
According to Cloudflare, the list of APIs Kitesurf supports has grown to include WebMCP, CSS Layout, the CSS Object Model (CSSOM), CSS Typed OM and custom elements. The company said it added URL-based module resolution, JSON modules and import map handling, and is using the new Cloudflare Workers module registry to support imports from URLs. Iframe behavior has also improved, it said, with better timing, isolation and text display across more languages and encodings.
Cloudflare said Kitesurf now passes more than 730,000 Web Platform Tests subtests, which it described as 500,000 more than at launch, and that it has decided to publish the results in the open so users can track them in real time.
On efficiency, the company said it reduced work crossing between its Boa engine and the DOM, so common reads such as getAttribute, id and parentNode can be answered inside the Wasm DOM. It also cited less repeated work on timers and script loading, memory release for unused objects, and lazy font loading. Despite added standards support, Cloudflare said wall-clock time and CPU usage remain roughly in line with its launch benchmarks and in some cases have improved.
Terminal rendering and open-source plans
Cloudflare said Kitesurf separates PageScript, the isolate that runs page code, from PageRenderer, which generates pixels, allowing rendering to be moved outside Kitesurf while security-critical parts stay server-side on its network. It compared the model to its Cloudflare Browser Isolation product.
To demonstrate this, the company said it moved PageRenderer to its Playground Worker and patched it to output to Kitty, a terminal graphics protocol supported by terminals including Kitty, Ghostty and WezTerm, plus a pure ANSI text mode. Cloudflare said the terminal version can be installed via brew and also sends back scrolling and click events.
The company said it remains committed to open-sourcing Kitesurf, calling it the elephant in the room, and that this is coming soon but it wants to be set up to support it long term. Kitesurf is available free while in beta, behind per-account limits, Cloudflare said.
What to do
- Try Kitesurf in the refreshed kitesurf.dev playground, or use it through Browser Run in your projects.
- To test WebMCP, open Cloudflare Radar in the Kitesurf playground and check the WebMCP entry on the Application tab of the DevTools panel.
- Point an AI agent at Kitesurf using the chrome-devtools-mcp configuration Cloudflare publishes, supplying your account ID and bearer token.
- Call Quick Actions such as screenshots, HTML extraction and PDF generation from a Worker script via the env.BROWSER.quickAction() binding.
- Install the terminal build with brew install cloudflare/cloudflare/kitesurf, then run kitesurf followed by a URL.
- Follow Cloudflare's published WPT results and changelog to track standards coverage as it changes.
Key facts and where they come from
- Kitesurf now supports WebMCP, Cloudflare said.
Today we are announcing that Kitesurf now supports WebMCP.
- Cloudflare says Kitesurf passes over 730,000 WPT subtests, 500,000 more than at launch.
We now pass 730,000+ WPT subtests and are growing. That's 500,000 more subtests than when we launched.
- Kitesurf has full Browser Run API coverage and works with CDP, Playwright, Puppeteer or MCP.
Starting today, Kitesurf has full Browser Run API coverage. You can use Kitesurf with CDP, Playwright, Puppeteer, or MCP.
- Performance remains roughly in line with launch benchmarks despite added standards support.
its wall-clock time and CPU usage remain roughly in line with our launch benchmarks, and in some cases they have improved
- Kitesurf can render pages in terminals using the Kitty graphics protocol, with an ANSI text fallback.
it outputs to Kitty—a terminal graphics protocol supported by modern terminals like Kitty itself, Ghostty, WezTerm, and others
- Cloudflare says it still plans to open-source Kitesurf.
we remain committed to open-sourcing Kitesurf. This is coming soon, but we want to do this right
- Kitesurf is free during beta with per-account limits.
It's available for free while in beta, behind per-account limits.