Browser Run adds WebMCP to Kitesurf and moves to document.modelContext
WebMCP now works in both Kitesurf and Lab sessions using the document.modelContext API from the WebMCP Community Group draft. Lab sessions no longer expose navigator.modelContextTesting, and you can list and run page tools via Chrome DevTools, AI agents, or CDP clients.
WebMCP now works in Kitesurf sessions as well as Lab sessions. Both backends use the document.modelContext API from the WebMCP Community Group draft ↗︎. Lab sessions no longer expose navigator.modelContextTesting.
To list and run page tools:
- Chrome DevTools: Use the Application > WebMCP panel in the live view of a Lab session or in the Kitesurf playground ↗︎.
- AI agents: Start Chrome DevTools MCP with the
--category-experimental-webmcpflag to add thelist_webmcp_toolsandexecute_webmcp_tooltools. - CDP clients: Use the
WebMCPCDP domain.
Source: original entry ↗
More from Cloudflare
Follow Cloudflare to get its new changes in your feed and email digest.
Cloudflare API MCP server now serves Cloudflare skills
The Cloudflare API MCP server now integrates with the Skills over MCP extension, allowing MCP clients to discover and access Cloudflare skills. Users can add the MCP server endpoint to compatible MCP clients to access these skills.
WAF failed detections field now available in Rules
A new cf.appsec.request.failed_detections field lets you control how rules handle requests when security detections fail. This array of detection IDs covers content scanning, WAF attack scoring, attack signatures, leaked credentials, and AI-based PII/prompt injection/custom topic detection failures, and works across custom rules, rate limiting rules, and request header transform rules.
Markdown for Agents: More efficient in-process streaming conversion
Markdown for Agents now uses an in-process streaming engine at the edge to convert HTML, reducing overhead and memory use. The conversion limit increased from 2 MiB to 6 MiB, and token count headers are no longer generated.