Browser Use
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
Descripción del creador (original en inglés)
Stealth Chrome for AI agents: bot-protected sites, Turnstile, closed Shadow DOM, clean Markdown.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"browser-scraper": {
"command": "npx",
"args": [
"-y",
"@eurafaeldecarvalho/browser-scraper",
"mcp"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add browser-scraper -- npx -y @eurafaeldecarvalho/browser-scraper mcpPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"browser-scraper": {
"command": "npx",
"args": [
"-y",
"@eurafaeldecarvalho/browser-scraper",
"mcp"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"browser-scraper": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@eurafaeldecarvalho/browser-scraper",
"mcp"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub eurafaeldecarvalho, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.8.3) llegó al registro hace 10 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Browser Use, Chrome DevTools MCP, MCP Server Browser
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
MCP server for Chrome DevTools
MCP server for browser use access
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Undetected Chrome for Node.js that reads and operates the sites that block bots. Use it as a library, a CLI or an MCP server for Claude, Cursor and Codex. It turns any page, including closed Shadow DOM and cross-origin iframes, into clean Markdown, structured data or an accessibility snapshot an agent can click through. Local, free, MIT, bring-your-own-LLM.
CreepJS: 0% headless, 0% stealth · `bot.sannysoft.com`: 0 failures · no `Runtime.enable` leak (what that means, and where it stops)
Recorded on one desktop PC: the Turnstile test page at nowsecure.nl in headless mode, bot.sannysoft.com headful on the PC's own GPU.
import { scrape } from "@eurafaeldecarvalho/browser-scraper";
const page = await scrape({ url: "https://example.com", formats: ["markdown", "metadata"] }); console.log(page.tier); // "http" | "browser" | "stealth": the cheapest tier that worked console.log(page.markdown); // clean, LLM-ready Markdown of the main content
# Give Claude Code a browser that gets through Cloudflare:
claude mcp add browser-scraper -- npx -y @eurafaeldecarvalho/browser-scraper mcp
@eurafaeldecarvalho/browser-scraper drives real Chrome over the raw DevTools Protocol (CDP). It never sends Runtime.enable, one of the most widely fingerprinted automation signals, and every layer of the browser's identity tells the same story. On top of that stealth core it adds the pieces AI workloads need: Markdown and metadata extraction, an accessibility snapshot with clickable refs, a one-call scrape() that escalates from plain HTTP to a stealth browser only when it has to, an MCP server, and optional LLM extraction with any model.
Why this one:
Runtime.enable leak, the persona (UA, Client Hints, WebGL, timezone, locale) is coherent, and mouse and keyboard input are human-like. solveTurnstile() handles Cloudflare's checkbox.find(), markdown() and snapshot() all reach into closed shadow roots and cross-origin iframes, which Playwright's snapshot and Readability-style extractors miss.{{SECRET}} placeholders so the model never sees them, an allow-list restricts domains, and page content is fenced as untrusted data.generateExtractor() has the model write CSS selectors once. After that run() extracts with no LLM, and runOrHeal() regenerates the selectors when the site changes.With the right setup — a clean residential/mobile IP, plus a real GPU (EC2 g4dn/g5) for render-hash targets — browser-scraper is built to clear the fingerprint suites and anti-bot stacks that block headless automation:
| Detection / fingerprint suite | Anti-bot / WAF vendor | ||
|---|---|---|---|
bot.sannysoft.com — 0 failures | ✅ | Cloudflare (Turnstile) | ✅ |
| CreepJS — 0% headless, 0% stealth | ✅ | DataDome | ✅ |
bot-detector.rebrowser.net | ✅ | Kasada | ✅ |
| Pixelscan | ✅ | Akamai Bot Manager | ✅ |
| IPHey | ✅ | PerimeterX / HUMAN | ✅ |
| Browserscan | ✅ | Imperva (Incapsula) | ✅ |
| Incolumitas | ✅ | Shape / F5 | ✅ |
| Fingerprint.com | ✅ | AWS WAF Bot Control | ✅ |
A ✅ means the fingerprint + behavior layer passes — it is not a guaranteed bypass. Against hard targets your IP reputation is the ceiling: a datacenter ASN loses before the JavaScript runs, so route through a residential/mobile proxy (see The production stack).
browser-scraperis not a CAPTCHA solver — for reCAPTCHA v2 / hCaptcha / Arkose (FunCaptcha) image challenges, pair it with a solver service. It *does* keep reCAPTCHA v3 scores high via human-like input and warmed profiles.
Numbers were taken on a desktop Chrome. On a GPU-less Lambda running chrome-headless-shell (
@sparticuz/chromium) the surfaces differ — re-run the suites against your *actual* production binary and treat that as the source of truth (see Cloud deployment).
This is a precision tool, not a magic bypass — it's honest about its edges (see Notes & limitations), and that honesty is exactly what makes the green checks above worth anything.
scrape(), snapshot + refs, MCP server, CLI, LLM extractionnpm install @eurafaeldecarvalho/browser-scraper
or:
pnpm add @eurafaeldecarvalho/browser-scraper
Requires Node.js ≥ 20 and a local Chrome/Chromium (it's found automatically, or point at one with chromePath). For AWS Lambda, also install the optional @sparticuz/chromium — see Cloud deployment. Profile history seeding uses Node's built-in node:sqlite (Node ≥ 22.5) or the optional better-sqlite3; if neither is available it is simply skipped. The LLM helpers need ai (and zod if you use Zod schemas), and only if you import /ai.
import { Browser } from "@eurafaeldecarvalho/browser-scraper";
const browser = new Browser();
try { const tab = await browser.newTab(); await tab.goto({ url: "https://example.com" });
const heading = await tab.find({ selector: "h1" }); console.log(await heading?.text());
await tab.screenshot({ path: "example.png" }); } finally { await browser.close(); }
That's the whole shape of the library: a Browser, a Tab, and Elements you find and act on. Everything below is detail on top of these three.
const tab = await browser.newTab();
await tab.goto({ url: "https://shop.example.com/product/42" });
const { markdown, title, links, wordCount } = await tab.markdown({ mainContent: true, // drop nav/header/footer/cookie banners (default) query: "price shipping", // optional: keep only the relevant blocks (BM25), saves tokens links: "inline", // "inline" | "reference" | "none" includeIframes: false, // true = also inline iframe documents, cross-origin included });
const meta = await tab.metadata(); // { title, description, canonical, lang, image, openGraph, twitter, jsonLd: [...] } // JSON-LD often already has the price, rating and availability: check it before you prompt.
markdown() reads Chrome's own DOM tree over CDP (DOM.getDocument with pierce). No script is injected into the page, and the content of closed shadow roots is included in reading order, with slots composed. For HTML you already have, htmlToMarkdown(html) and extractMetadata(html) do the same without a browser.
scrape(): one call, cheapest tier firstimport { Browser, scrape } from "@eurafaeldecarvalho/browser-scraper";
const browser = new Browser({ proxy: process.env.PROXY }); // reuse it across URLs const page = await scrape({ url, browser, formats: ["markdown", "metadata", "links", "html", "screenshot"], strategy: "auto", // http → browser → stealth (or pin one tier) http: { curlImpersonate: "curl_chrome131" }, // optional: real Chrome TLS for the http tier });
page.tier; // which tier produced the result page.attempts; // [{ tier: "http", ok: false, reason: "needs JavaScript (empty app shell)", ms: 4 }, …]
| Tier | What runs | Used when |
|---|---|---|
http | One request, no Chrome (Node fetch, or curl-impersonate for a genuine Chrome JA3/JA4) | Static pages, APIs |
browser | The stealth Chrome | The HTTP response was blocked (403/429/503), a challenge, or an empty JS app shell |
stealth | The same tab plus a behavioral warm-up and an interactive Turnstile solve | The browser still sees a challenge page |
A challenge page is never returned as content: if every tier is blocked, scrape() throws a ScrapeError that carries the attempts.
console.log(await tab.snapshot());
// - main // - heading "Sign in" [level=1] // - textbox "Email" [ref=e3] // - button "Continue" [ref=e4] // - Iframe [ref=e5] // - checkbox "Verify you are human" [ref=e6] ← cross-origin iframe, still addressable
await (await tab.byRef({ ref: "e3" })).type({ text: "me@example.com" }); // human-like typing await (await tab.byRef({ ref: "e4" })).click(); // human-like mouse
The accessibility tree is computed on the composed tree, so elements inside closed shadow roots appear and can be clicked. Pass { interactive: true } to get just the flat list of clickable or typeable elements.
claude mcp add browser-scraper -- npx -y @eurafaeldecarvalho/browser-scraper mcp
Or in any MCP client config (claude_desktop_config.json, .cursor/mcp.json, …):
{
"mcpServers": { "browser-scraper": { "command": "npx", "args": ["-y", "@eurafaeldecarvalho/browser-scraper", "mcp", "--allowed-domains", "example.com", "--secrets", "/path/to/.env"] } } }
Tools:
| Tool | What it does |
|---|---|
navigate | Opens a URL and returns the snapshot |
snapshot | Accessibility outline with [ref=…] |
click | Clicks an element by ref, with human-like input |
type | Types into an element by ref, with human-like input |
press_key | Presses a key |
go_back | Goes back in history |
wait | Waits a number of seconds |
| markdown | Ma
Solo se muestra el principio; lee el resto en el repo