About Cf Browser Cdp
Cf Browser Cdp is an MCP server in the Browser category: connect Cloudflare Browser Rendering via CDP (Chrome DevTools Protocol).
Install
git clone https://github.com/miantiao-me/cf-browser-cdpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Cf Browser Cdp
Powered by Claude · Grounded in docs
Security checks
- ✓README presentThe repository ships documentation.
5 checks have not been run yet.
README
Cloudflare Browser CDP
Connect Cloudflare Browser Rendering via CDP (Chrome DevTools Protocol).
Wraps Cloudflare's Browser Rendering service as a standard CDP WebSocket endpoint, so any CDP-compatible tool can connect directly.
How It Works
CDP Client ←→ [Worker: Auth + Proxy] ←→ [Cloudflare Browser Rendering]
- Client opens a WebSocket connection to the Worker
- Worker verifies token, calls
/v1/acquirevia theBROWSERbinding to obtain a browser session - Worker establishes an upstream WebSocket to Cloudflare Browser Rendering
- CDP messages are transparently forwarded in both directions, with a 4-byte little-endian length-prefixed chunking protocol for large messages (~1MB Cloudflare WebSocket frame limit)
The Worker also serves a /json/version endpoint returning CDP version info and WebSocket debugger URL, compatible with the standard CDP discovery protocol.
Usage
After deployment, the Worker URL is a standard CDP endpoint (CDP_ENDPOINT in examples below).
Chrome DevTools MCP
chrome-devtools-mcp lets AI coding agents control a browser via Chrome DevTools.
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["chrome-devtools-mcp@latest", "--wsEndpoint=wss://CDP_ENDPOINT?token=YOUR_TOKEN"]
}
}
}
Playwright MCP
playwright-mcp provides browser automation via Playwright as an MCP server.
{
"mcpServers": {
"playwright": {
"command": "npx",
"args": ["@playwright/mcp@latest", "--cdp-endpoint=wss://CDP_ENDPOINT?token=YOUR_TOKEN"]
}
}
}
Agent Browser
agent-browser is a browser automation CLI for AI agents.
agent-browser --cdp "wss://CDP_ENDPOINT?token=YOUR_TOKEN" open https://example.com
agent-browser snapshot -i
agent-browser click @e1
Server Configuration
Prerequisites
- A Cloudflare account with Browser Rendering enabled (Free plan: 10 min/day, Paid plan: 10 hrs/month)
- Node.js and pnpm
Deploy
git clone https://github.com/miantiao-me/cf-browser-cdp.git
cd cf-browser-cdp
pnpm install
pnpm deploy
Auth Token
npx wrangler secret put BROWSER_TOKEN
All requests must include authentication:
- Authorization header:
Authorization: Bearer <token> - URL query parameter:
?token=<token>(for WebSocket connections)
Query Parameters
| Parameter | Default | Description |
|---|---|---|
token |
— | Auth token (for WebSocket connections) |
keep_alive |
120000 |
Browser session keep-alive duration in milliseconds |
Environment Variables
| Variable | Required | Description |
|---|---|---|
BROWSER_TOKEN |
Yes | Auth token for securing access |
Cloudflare Bindings
| Binding | Type | Description |
|---|---|---|
BROWSER |
Browser Rendering | Browser Rendering service binding, configured in wrangler.jsonc |
Development
pnpm dev # Start local dev server (0.0.0.0)
pnpm start # Start local dev server (localhost)
pnpm lint # Run formatter and linter
pnpm cf-typegen # Regenerate Cloudflare binding types
License
MIT
README copy captured when this server was indexed; it may lag the repository. The original is authoritative.