Skip to directory

Cloudflare Browser Run MCP

Cloudflare

Streamable HTTP13 documented tools15

About Cloudflare Browser Run MCP

Cloudflare's hosted Browser Run server gives MCP clients browser access for fetching pages, converting them to Markdown and taking screenshots. Browser Run (formerly Browser Rendering) also offers a separate account-scoped CDP setup for full browser automation.

What you can use it for

  • Fetch public web pages and return Markdown
  • Take screenshots of web pages
  • Use hosted browser automation through the separately documented CDP connection
Connection and setup
Hosting
Remote, vendor-hosted
Transport
Streamable HTTP
Endpoint
https://browser.mcp.cloudflare.com/mcp
Authentication
The public Browser Run MCP URL is listed in Cloudflare's server catalog; its client authentication flow is not described in the opened setup source. Do not conflate it with the separate account-specific CDP integration, which uses a Cloudflare API token with Browser Rendering - Edit permissions.

Requirements

  • Compatible MCP client
  • Cloudflare account and Browser Rendering service for account-scoped CDP/browser sessions; availability and billing depend on the selected Browser Run feature

Setup steps

  1. Add https://browser.mcp.cloudflare.com/mcp as a remote HTTP/Streamable HTTP server in a client that supports remote MCP.
  2. If using the distinct account-scoped CDP browser workflow instead, create a Cloudflare API token with Browser Rendering - Edit permission, then follow the Browser Run MCP client guide for the chrome-devtools-mcp package and account-specific WebSocket endpoint.
  3. Restart/reconnect the client and verify with a safe page fetch or screenshot request.
Tools 13

The typed Browser Run server reference describes this product-specific endpoint. Its documented 13-tool list covers fetch/render, extraction, crawl and browser-session operations; it is distinct from the Browser Run REST API and the Cloudflare API Code Mode server.

  • get_url_html_content

    Fetch rendered page HTML.

    01
  • get_url_markdown

    Fetch a page converted to Markdown.

    02
  • get_url_screenshot

    Capture a page screenshot.

    03
  • get_url_pdf

    Render a page to PDF.

    04
  • get_url_snapshot

    Return page content and a screenshot together.

    05
  • scrape_url_elements

    Extract page elements by CSS selector.

    06
  • get_url_json

    Extract structured JSON data from a page.

    07
  • get_url_links

    Retrieve links from a page.

    08
  • start_crawl

    Start a crawl of website content.

    09
  • get_crawl_result

    Retrieve crawl results.

    10
  • cancel_crawl

    Cancel a running crawl.

    11
  • list_browser_sessions

    List browser sessions.

    12
  • kill_browser_session

    Terminate a browser session.

    13
Limitations and notes
  • The generic Browser Run remote MCP entry is distinct from account-specific CDP access documented with chrome-devtools-mcp; they have different setup and credentials.
  • Browser Run capabilities, quotas and charges depend on Cloudflare account and product settings.
  • Exact tool names and the generic endpoint authentication flow were not established from the accessible primary source.
Source discrepancies
  • The discovery name ?Cloudflare Browser Rendering? corresponds to the current Cloudflare product name Browser Run and can refer either to its generic hosted MCP or to account-specific CDP automation. This record uses the official generic Browser Run MCP endpoint and explicitly describes CDP as a separate path.
Original sources
  • official tool reference

    Cloudflare lists Browser Run as a product-specific remote MCP endpoint. This is separate from Browser Run REST Quick Actions and the Cloudflare API Code Mode endpoint; tool availability and auth depend on the server and account.

  • official documentation or source

    Cloudflare lists Browser Run as a product-specific remote MCP endpoint. This is separate from Browser Run REST Quick Actions and the Cloudflare API Code Mode endpoint; tool availability and auth depend on the server and account.

Documentation checked 2026-10-28T12:50:00.000Z. Connection has not been runtime tested.