Cloudflare's Agent Browser Can Now Use a Website's Tools

Cloudflare updated Kitesurf on September 28 so an AI agent using its browser can call a website’s exposed tools. For a small software company’s marketing team, that changes the test of an agent-ready site: can the agent complete a product search, book a demo, or reach the right support answer in the browser it actually uses?

Cloudflare built Kitesurf as a lighter browser for AI agents and launched it in August. Its latest release adds WebMCP, a way for a site to offer named actions to an agent instead of making it find buttons and click through pages. Celso Martinho, the author of Cloudflare’s announcement, puts the problem in one sentence:

“Websites were not built for agents to use.”

The site and the browser now have to meet. Our Shopify story covered one side: stores exposing tools that let agents search products and assemble carts. Kitesurf’s update covers the other side: a browser built for agents can now discover and run those tools. That’s a new capability, not evidence that agents are already buying at scale.

The browser can act on a site’s menu

Think of WebMCP as a menu of actions a site chooses to offer. A travel site might expose a flight-search function; a software company might eventually expose a product search or a way to request a demo. The agent calls the action directly and receives a structured result. It doesn’t have to guess which part of a visual page to click.

Cloudflare says an agent connected to Kitesurf can inspect that menu and run its entries. Its developer changelog names the two functions available through Chrome DevTools MCP, list_webmcp_tools and execute_webmcp_tool, and says the site interface now uses document.modelContext. A developer can also inspect the tools in the WebMCP panel of Kitesurf’s public playground.

That’s the change marketing teams should notice. A site can have beautiful pages and still give an agent a poor route to an answer or action. Adding a tool isn’t a win if the browser can’t call it, or if the tool returns thin, stale information. The handoff between site and browser is where the customer experience now needs checking. We saw the same issue from the publisher side in our earlier WebMCP reporting.

The update reaches beyond a demo. Cloudflare says Kitesurf now works across the full Browser Run API, including the connections used by Playwright, Puppeteer and agents using MCP. It has also added support for more page features, including custom elements and modern JavaScript imports. Those changes matter because an agent browser has to render the real site before its tools are useful. Cloudflare’s original Kitesurf launch was about a browser built around machine tasks. This release makes it more capable on actual websites.

The beta still has limits

Cloudflare’s own Kitesurf documentation gives a useful boundary. The browser is free during beta, with account limits. It can’t yet handle video or WebGL, certain bot challenges, or long authenticated sessions that need persistent state. Cloudflare recommends its Chromium browser for those jobs. Its published comparison also shows Kitesurf using less computing power and memory while taking longer to capture screenshots and extract page text. Those are vendor-run tests on 14 URLs, not proof that every marketing site works better.

Kevin Riedl, Wavect’s managing director for operations and product, made the same practical point in an August review. The review predates this WebMCP release, and Wavect says it didn’t run an independent benchmark. Its advice on browser choice still applies:

“Keep a Chromium fallback until your own task corpus proves accepted-result parity.”

In plain terms: keep a full browser available until the lighter one passes the tasks you care about. A successful connection is only the beginning. An agent still needs to reach the right page, use the right tool, get an accurate result, and stop before an action that requires approval.

WebMCP itself remains a Community Group draft, and Cloudflare hasn’t published a conversion or usage figure for Kitesurf’s new support. A test run can show whether your own site works; it can’t tell you how many customers are sending agents there today.

A test for the marketing team

Pick three tasks a buyer or prospect would actually give an assistant. For a B2B software site, those might be finding a plan for a team of 20, locating a security answer, and getting to a demo request. First, open your site in Kitesurf’s public playground and inspect the WebMCP panel. Then have a teammate connect an agent through the documented MCP option and run the three tasks. Record which tools appear, what they return, and where the agent has to fall back to clicking. Repeat in a full browser for tasks Kitesurf can’t finish.

The verdict is a short list of broken handoffs, not a badge that says your site is ready for agents. Fix the product facts and site actions the browser can use. Keep a human approval step where the action spends money, changes an account, or sends information. Cloudflare has put another agent browser on the WebMCP side of the table. Your site still has to give it something worth doing.