Cloudflare Browser Rendering Experiments & MCP Server

Created By
amotivva year ago
This project demonstrates how to use Cloudflare Browser Rendering to extract web content for LLM context. It includes experiments with the REST API and Workers Binding API, as well as an MCP server implementation that can be used to provide web context to LLMs.
Overview

What is Cloudflare Browser Rendering?

Cloudflare Browser Rendering is a project that demonstrates how to extract web content for LLM context using Cloudflare's Browser Rendering capabilities. It includes experiments with the REST API and Workers Binding API, along with an MCP server implementation.

How to use Cloudflare Browser Rendering?

To use this project, clone the repository, install the necessary dependencies, and set up a Cloudflare Worker with the provided examples. You can run various experiments to fetch and process web content.

Key features of Cloudflare Browser Rendering?

  • Integration with Cloudflare's Browser Rendering for web content extraction.
  • Support for REST API and Workers Binding API.
  • MCP server for processing web content for LLMs.
  • Example implementations and utilities for easy setup.

Use cases of Cloudflare Browser Rendering?

  1. Extracting web content for use in language models.
  2. Automating web scraping tasks using Cloudflare's infrastructure.
  3. Providing web context to LLMs for enhanced responses.

FAQ from Cloudflare Browser Rendering?

  • What are the prerequisites for using this project?

You need Node.js (v16 or later), a Cloudflare account with Browser Rendering enabled, TypeScript, and Wrangler CLI for deployment.

  • Is there a license for this project?

Yes, this project is licensed under the MIT License.

  • How can I run the experiments?

You can run the experiments by executing the provided npm scripts for each experiment type.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
amotivv
Star
1
Language
TypeScript
License
MIT license

Recommend Servers

View All
Docwand

14 hours ago
//beforeyouship — LLM Cost Modeling From Your Editor
@Indiegoing

Query realistic LLM cost models without leaving your editor. beforeyouship models the **true monthly cost** of an LLM app architecture — retries, prompt caching, batch discounts, infra overhead, and 3×/10× growth — across GPT-5.x, Claude, Gemini, DeepSeek, and more. Not a token calculator: a planning tool for the design phase, before you commit to a stack. **No API key needed to try it** — demo mode covers the six free-tier models. A Pro key from [beforeyouship.dev](https://beforeyouship.dev) unlocks the full 18-model catalog. ## What you can ask - "How much will a RAG chatbot cost at 10,000 requests/day?" - "Compare Claude Haiku vs Gemini Flash pricing for my workload" - "What's the cheapest model for a multi-step agent at scale?" - "Show me current per-token prices for Anthropic models" ## Tools ### `estimate_cost` Full cost model for an architecture at a given usage level. Returns Naive / Realistic / Worst Case monthly cost per model, 3×/10× growth scenarios, and an opinionated recommendation with reasoning. ### `get_model_prices` Current per-1M-token pricing — input, output, cached input, batch — with context windows and staleness metadata. ### `list_archetypes` Seven preset architecture patterns (simple chatbot, chatbot with history, RAG pipeline, multi-model router, coding assistant, document processor, multi-step agent) used as starting points for estimates. ## Setup **Claude Code:** ​```bash claude mcp add --transport http beforeyouship https://beforeyouship.dev/api/mcp ​``` **Cursor / other clients** — add a remote server: ​```json { "mcpServers": { "beforeyouship": { "type": "streamable-http", "url": "https://beforeyouship.dev/api/mcp" } } } ​``` Add an `Authorization: Bearer bys_...` header with a Pro key for the full catalog. ## Try it > Estimate the monthly cost of a RAG pipeline at 10,000 requests/day

14 hours ago