I tried to use the Chrome DevTools MCP URL allowlist with Cloudflare Kitesurf, but ran into Chrome version requirements
This page has been translated by machine translation. View original
Introduction
When entrusting a browser operation agent with an internal staging site, you will want to restrict the destinations to prevent navigation to unintended URLs. Chrome DevTools MCP provides --allowedUrlPattern, which allows only specified URLs.
Kitesurf is a browser for AI agents running on Cloudflare Workers. It supports the Chrome DevTools Protocol (CDP) and can be used from browser operation agents via Chrome DevTools MCP.
When I added Kitesurf to a Chrome for Testing configuration that was already using this setting, the connection succeeded, but an error related to Chrome's version requirements occurred on the very first screen operation.
After investigating, I found that the Chrome version reported by Kitesurf and the version required by Chrome DevTools MCP 1.6.0 for the URL allowlist did not match. This article presents what I confirmed and the diagnostic results with the URL allowlist removed.
Target Audience
- Those who want to operate Kitesurf from Chrome DevTools MCP
- Those who are restricting destinations with
--allowedUrlPattern - Those who want to understand the error related to Chrome version requirements
Verification Environment
- Date confirmed: August 11, 2026
- Chrome version returned by Kitesurf:
Chrome/145.0.0.0 - Chrome DevTools MCP: 1.6.0
- Browser for comparison: Chrome for Testing 150.0.7871.24
- Agent used to operate the browser: Codex (model used:
gpt-5.6-sol)
Note that the connection to Kitesurf uses an API token with Browser Rendering - Edit permission.
References
Issue: URL Allowlist Error
In the initial comparison, I specified only the staging site in Chrome DevTools MCP's --allowedUrlPattern. The CDP connection to Kitesurf succeeded, but the following error appeared on the first screen operation.
The allowlist option require Chrome 149 or greater.
Cause: Chrome Version Requirement
I checked the information returned by Kitesurf via CDP's Browser.getVersion.
| Item | Result |
|---|---|
| CDP protocol | 1.3 |
| Product identifier | Chrome/145.0.0.0 |
| Revision | @kitesurf |
The official Chrome DevTools MCP README states that --allowedUrlPattern requires Chrome 149 or higher. Under the conditions of this test, it was not possible to use Kitesurf's reported Chrome 145 together with --allowedUrlPattern.
While the browsers officially supported by Chrome DevTools MCP are Google Chrome and Chrome for Testing, Cloudflare publishes a configuration example for using Kitesurf with Chrome DevTools MCP. This error occurred when I tried to verify whether the URL allowlist could be used with this combination.
Verification: Operation Without URL Allowlist
The official Kitesurf MCP configuration example uses --wsEndpoint and --wsHeaders, but does not specify --allowedUrlPattern. Therefore, without modifying the original comparison results, I ran a separate diagnostic with the URL allowlist removed.
In the diagnostic, I restricted the available MCP operations to the following:
- Listing pages
- Navigating to a specified URL
- Taking a snapshot of the page structure
- Capturing a screenshot
- Closing a page
I opened the form screen of the staging site in Kitesurf and confirmed the display indicating React initialization had completed. I also confirmed that screenshots could be taken. I checked the destination URLs included in the execution log and confirmed there was no navigation to any URLs that had not been permitted.
Discussion
I believe it is difficult to introduce the current combination as-is into an environment where a URL allowlist is mandatory. While removing the setting allows Kitesurf to operate, doing so means weakening security requirements in order to make it work.
For staging sites that do not contain sensitive information, there is room to try an approach of limiting available MCP operations and auditing destinations after execution. However, post-execution auditing cannot stop unintended communications before they occur. When operating production environments or admin panels, it is better not to rely solely on this approach until a proactive control equivalent to the URL allowlist can be put in place.
Summary
With Chrome 145 as reported by Kitesurf, it was not possible to use --allowedUrlPattern with Chrome DevTools MCP 1.6.0. Removing this option allowed page operations and screenshot capture to work with Kitesurf as well. However, it is important to note that limiting MCP operations and auditing destination URLs after execution is not the same as a URL allowlist that proactively blocks navigation. I hope this article serves as a helpful reference for version requirements and security configuration when combining Kitesurf with Chrome DevTools MCP.
