Browser Use
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
作者提供的说明(英文原文)
Stealth Chrome for AI agents: bot-protected sites, Turnstile, closed Shadow DOM, clean Markdown.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"browser-scraper": {
"command": "npx",
"args": [
"-y",
"@eurafaeldecarvalho/browser-scraper",
"mcp"
]
}
}
}在终端中运行这条命令
claude mcp add browser-scraper -- npx -y @eurafaeldecarvalho/browser-scraper mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"browser-scraper": {
"command": "npx",
"args": [
"-y",
"@eurafaeldecarvalho/browser-scraper",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"browser-scraper": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@eurafaeldecarvalho/browser-scraper",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 eurafaeldecarvalho 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.8.3)于10天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Browser Use, Chrome DevTools MCP, MCP Server Browser
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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
只显示了开头部分;其余内容请在仓库中阅读