What are the prerequisites?
Node.js v18 or higher, a Cloudflare account with Browser Rendering API access, and a Cloudflare Worker deployed with the provided `puppeteer-worker.js` file, plus a KV namespace named `SCREENSHOTS`.
@amotivv
Basic information
This MCP server provides tools for interacting with Cloudflare Browser Rendering, allowing you to fetch and process web content for use as context in LLMs directly from Cline or Claude Desktop.
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"cloudflare-browser-rendering-mcp": {
"command": "npx",
"args": [
"-y",
"@smithery/cli",
"install",
"@amotivv/cloudflare-browser-rendering-mcp",
"--client",
"claude"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
Fetch the live tool list by running this server in a temporary sandbox using the button above.
This MCP (Model Context Protocol) server provides tools for fetching and processing web content using Cloudflare Browser Rendering for use as context in LLMs. It is designed to work with both Claude and Cline client environments.
Install via Smithery (npx -y @smithery/cli install @amotivv/cloudflare-browser-rendering-mcp --client claude) or manually from GitHub. Configure the BROWSER_RENDERING_API environment variable with the URL of a deployed Cloudflare Worker that has Browser Rendering and KV bindings. Once configured, tools like fetch_page, search_documentation, extract_structured_content, summarize_content, and take_screenshot become available in the client.
Node.js v18 or higher, a Cloudflare account with Browser Rendering API access, and a Cloudflare Worker deployed with the provided `puppeteer-worker.js` file, plus a KV namespace named `SCREENSHOTS`.
Set the environment variable in the MCP server configuration (e.g., `claude_desktop_config.json` or `cline_mcp_settings.json`) with the URL of your deployed Cloudflare Worker, like `"BROWSER_RENDERING_API": "https://your-worker-url.workers.dev"`.
Five tools: `fetch_page`, `search_documentation`, `extract_structured_content`, `summarize_content`, and `take_screenshot`. Each accepts specific parameters listed in the README.
A Browser Rendering binding named `browser` and a KV namespace binding named `SCREENSHOTS`. Without these, the worker will return errors.
Run `npm test` after building the project and setting the `BROWSER_RENDERING_API` environment variable. This starts the MCP server and tests each tool with sample requests.

An MCP server for generating images from HTML & CSS or screenshots of URLs using htmlcsstoimage.com.
🔮 Platform-neutral Browser Use for AI agents: real Chrome automation with a CLI + SDKs, no lock-in, dead simple.
This MCP server provides browser automation capabilities through Puppeteer, allowing interaction with both new browser instances and existing Chrome windows.

Model Context Protocol Servers
Let Claude Code, Claude Desktop, OpenAI Codex, Kimi and any MCP-capable AI agent create, launch, check and drive browser profiles in Nullprint, the AI antidetect browser. Install with one command.
Comments