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)
Drive a stealth-patched Chromium daemon: navigate, screenshot, eval JS, attach over CDP.
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.
BROWSER_USE_API_KEY, BROWSER_USE_URLLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
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": {
"sendblue-browser": {
"command": "npx",
"args": [
"-y",
"sendblue-browser-mcp"
],
"env": {
"BROWSER_USE_API_KEY": "your-value",
"BROWSER_USE_URL": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add sendblue-browser --env BROWSER_USE_API_KEY=your-value --env BROWSER_USE_URL=your-value -- npx -y sendblue-browser-mcpCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"sendblue-browser": {
"command": "npx",
"args": [
"-y",
"sendblue-browser-mcp"
],
"env": {
"BROWSER_USE_API_KEY": "your-value",
"BROWSER_USE_URL": "your-value"
}
}
}
}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": {
"sendblue-browser": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"sendblue-browser-mcp"
],
"env": {
"BROWSER_USE_API_KEY": "your-value",
"BROWSER_USE_URL": "your-value"
}
}
}
}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.
BROWSER_USE_URL envEsta 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 6 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub sendblue-api, 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.
Debes completar: BROWSER_USE_API_KEY
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.2.3) llegó al registro hace 5 meses.
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.
A standalone debug browser for agents. Stealth-patched Chromium behind a tiny HTTP API, with persistent named sessions, an easy purge endpoint, configurable auto screenshots, and CDP attach so any client (Playwright, Puppeteer, undetected-chromedriver, custom scripts) can drive it.
It runs as its own process — not tied to any one Claude / Cursor / Codex session — so multiple agents can share it concurrently, debug each other's flows, and reuse a logged-in session without paying the auth tax every run.
| Need | What you get |
|---|---|
| Not coupled to a single agent | Long-running HTTP daemon. Any tool with a bearer token can drive it. |
| Doesn't look automated | Chromium patched via patchright: navigator.webdriver is hidden, CDP detection vectors are patched, real Chromium binary (no Playwright fingerprints). Passes typical Cloudflare Turnstile and similar low-friction checks; not for hostile scraping at scale. |
| Reusable sessions | Named persistent profiles. Log in once, every subsequent debug run reuses the cookies. |
| One-click reset | POST /sessions/:name/purge clears cookies + active-page storage but keeps the session id, so your client code keeps working. |
| Multi-agent friendly | Each session is an isolated BrowserContext (or its own profile). Run 5+ debug sessions in parallel without state bleed. |
| CDP attach | GET /sessions/:name/cdp-url returns the shared browser CDP URL for non-persistent sessions, so Playwright / Puppeteer / any CDP client can connect() to the debug browser. |
| Auto evidence | Navigation screenshots follow NAV_SCREENSHOT_POLICY (default: headless only). Optional Playwright traces. |
| HTTP-controlled | Plain curl works. No SDK required. |
| Self-contained deploy | One docker compose up on any Mac mini / EC2 / Codespace. No host Chromium needed. |
Prereqs: Bun >=1.3 and Node.js >=20 on your PATH.
git clone https://github.com/sendblue-api/sendblue-browser-use.git
cd sendblue-browser-use bun install bun --bun x patchright install chromium
cp .env.example .env
TOKEN="$(openssl rand -hex 32)" sed -i.bak "s/^BROWSER_USE_API_KEY=.*/BROWSER_USE_API_KEY=$TOKEN/" .env rm .env.bak
bun run dev
Then in another terminal:
source .env
TOKEN="Authorization: Bearer $BROWSER_USE_API_KEY"
curl -s -X POST http://127.0.0.1:8787/sessions \ -H "$TOKEN" -H "Content-Type: application/json" \ -d '{"name":"qa","persistent":true}'
curl -s -X POST http://127.0.0.1:8787/sessions/qa/navigate \ -H "$TOKEN" -H "Content-Type: application/json" \ -d '{"url":"https://trybloom.so/"}'
curl -s http://127.0.0.1:8787/sessions/qa/screenshot?fullPage=true \ -H "$TOKEN" -o /tmp/qa.png
curl -s -X POST http://127.0.0.1:8787/sessions/qa/purge -H "$TOKEN"
echo "BROWSER_USE_API_KEY=$(openssl rand -hex 32)" > .env
docker compose up -d
Same API, exposed on 127.0.0.1:8787. Data persists in ./data/. CDP stays loopback-only inside the container by default; to attach CDP from the host, uncomment CDP_BIND and the 127.0.0.1:9222:9222 port mapping in docker-compose.yml on a trusted machine only.
The repo ships three packaging layers so any agent can drive the daemon with one line of config.
The cross-agent path. Wraps the HTTP API as MCP tools (health, create_session, navigate, screenshot, script, get_cdp_url, purge_session, etc).
{
"mcpServers": { "sendblue-browser": { "command": "npx", "args": ["-y", "sendblue-browser-mcp@0.2.3"], "env": { "BROWSER_USE_URL": "http://127.0.0.1:8787", "BROWSER_USE_API_KEY": " " } } } }
Drop into ~/.cursor/mcp.json, ~/Library/Application Support/Claude/claude_desktop_config.json, ~/.gemini/config/mcp_config.json, etc. For Codex:
codex mcp add sendblue-browser \
--env BROWSER_USE_URL=http://127.0.0.1:8787 \ --env BROWSER_USE_API_KEY= \ -- npx -y sendblue-browser-mcp@0.2.3
Wrapper source: mcp/.
/plugin install sendblue-api/sendblue-browser-use
Pulls .claude-plugin/plugin.json + skills/sendblue-browser/SKILL.md from this repo.
The same skills/sendblue-browser/SKILL.md works as a skill across Codex, Google Antigravity, and Cline. Copy the folder into:
| Agent | Path |
|---|---|
| Codex | ~/.codex/skills/sendblue-browser/ |
| Antigravity | ~/.gemini/skills/sendblue-browser/ |
| Cline | enable Skills in Settings, then drop in its skills directory |
If your repo already follows the agents.md convention, the AGENTS.md in this repo doubles as a copy-pasteable section for any consumer repo that wants to call this daemon.
All routes require Authorization: Bearer $BROWSER_USE_API_KEY except /health.
| Method | Path | Body / Query | Returns |
|---|---|---|---|
GET | /health | — | { ok, service, version, sessions, defaultHeadless, navScreenshotPolicy } |
GET | /sessions | — | { sessions: [...] } |
POST | /sessions | { name, persistent?, headless?, viewport?, userAgent?, locale?, timezone?, traces?, proxy? } | { session } |
GET | /sessions/:name | — | session info + current page url/title |
POST | /sessions/:name/purge | — | { session } — clear cookies + active-origin storage, keep session id |
DELETE | /sessions/:name | — | { ok } — close context, remove profile |
POST | /sessions/:name/navigate | { url, waitUntil?, timeoutMs? } | { url, title, status } |
GET | /sessions/:name/screenshot | ?fullPage=true&selector=... | image/png |
POST | /sessions/:name/script | { code, timeoutMs? } (≤200kB) | { result } — code runs in page context |
GET | /sessions/:name/cookies | ?url=... | { cookies } |
POST | /sessions/:name/cookies | { cookies: [...] } | { ok } |
GET | /sessions/:name/console | ?limit=100 | { messages: [...] } (ring buffer) |
GET | /sessions/:name/cdp-url | — | { cdpUrl, targetId } — for non-persistent sessions only |
POST /sessions/:name/script passes code directly to Playwright's page.evaluate. Send a JavaScript expression, or wrap statements in an IIFE. Scripts time out after 30s by default; pass timeoutMs up to 120000, or 0 to disable the request timeout.
{ "code": "(() => { const x = 1; return x; })()" }
All non-2xx responses share the same envelope. Failures from Playwright are truncated to one line before being returned; the full message is logged server-side with proxy credentials redacted.
{ "error": { "code": "navigate_failed", "message": "net::ERR_NAME_NOT_RESOLVED" } }
| Status | Code | Meaning |
|---|---|---|
| 400 | empty_body | request body is required but was missing |
| 400 | malformed_json | body was not valid JSON |
| 400 | invalid_body | body failed Zod validation (see error.details) |
| 401 | unauthorized | missing or wrong bearer token |
| 404 | not_found | session does not exist |
| 409 | already_exists | a session with that name is already running |
| 409 | cdp_unavailable_for_persistent_session | persistent sessions don't expose the shared CDP url |
| 422 | script_failed | /script request was valid but the in-page eval threw or timed out |
| 500 | internal_error | unexpected — check server logs |
| 502 | navigate_failed screenshot_failed cookie_read_failed cookie_write_failed session_unreachable | Chromium-side failure |
{
name: string; // required, [a-z0-9_-] persistent?: boolean; // default true — profile data survives restarts headless?: boolean | "new"; // persistent sessions only; non-persistent uses DEFAULT_HEADLESS viewport?: { width, height }; userAgent?: string; locale?: string; // default "en-US" timezone?: string; traces?: boolean; // capture a Playwright trace.zip on session close proxy?: { server, username?, password?, bypass? }; }
POST /sessions/:name/cookies accepts up to 500 Playwright-style cookies:
{
cookies: Array<{ name: string; value: string; url?: string; // absolute URL, or domain + path domain?: string; path?: string; expires?: number; httpOnly?: boolean; secure?: boolean; sameSite?: "Strict" | "Lax" | "None"; }>; }
Each cookie must include either url or both domain and path.
~/.sendblue-browser-use/profiles/ /. After a daemon restart, recreate the same named persistent session to reuse that profile. CDP attach is not available for these sessions because each gets its own private browser instance.BrowserContext. State is in-memory only. CDP attach IS available via /sessions/:name/cdp-url, which returns the shared browser-level CDP endpoint plus a targetId for the session page. CDP clients can see the shared debug browser, so keep the CDP port local and trusted and select the returned target before driving.Pick persistent for "log in once, debug for a week" workflows. Pick non-persistent when you need to attach Playwright / Puppeteer directly.
examples/attach-from-playwright.ts — connect Playwright over CDP and drive a page (run with Node/tsx as shown in the file header)examples/attach-from-puppeteer.ts — same with Puppeteerexamples/multi-agent-debug.ts — two agents driving two surfaces in parallelexamples/run-script.sh — curl-only walkthroughThis is built on patchright, a maintained fork of Playwright that:
navigator.webdriverWe deliberately do not pass --disable-blink-features=AutomationControlled or override userAgent/viewport by default — patchright handles those internally and our overrides would defeat its rebrowser patches. Pass an explicit userAgent per session only if you have a reason.
Why patchright over alternatives:
~/.sendblue-browser-use/
├── profiles/ │ └── / # persistent profile dir └── runs/ └── / ├── 2026-05-25T...-nav.png # automatic nav screenshot when policy enables it └── 2026-05-25T...-trace.zip # if traces:true at create
POST /sessions/:name/purge clears cookies and permissions context-wide, then clears localStorage, sessionStorage, IndexedDB, ServiceWorker registrations, CacheStorage, and the console buffer for c
Solo se muestra el principio; lee el resto en el repo