Browser Use
by browser-use
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Computer or cloud★ 120,087MITUpdated 17 days ago
Install
vibatchium
Overview
Description from the maker (original English)
Stealth browser automation for AI agents — real Chrome, N parallel persistent logged-in sessions.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Web & browsers
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- PyPIPython’s uv installed (for the uvx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"vibatchium": {
"command": "uvx",
"args": [
"vibatchium",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add vibatchium -- uvx vibatchium mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"vibatchium": {
"command": "uvx",
"args": [
"vibatchium",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"vibatchium": {
"type": "stdio",
"command": "uvx",
"args": [
"vibatchium",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account trueoriginlabs, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Web & browsersi
- More stars than 0% of the other 878 servers in this category
- Published to the registry more recently than 97% of the other 878 servers in this category
- Basic checks equal to or better than 100% of the other 878 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is vibatchium safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.21.0) reached the registry today.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
What can I use instead?
In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Chrome DevTools MCP
by ChromeDevTools
Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.
Runs on your computer★ 54,821Apache-2.0Updated 15 days ago
Install
MCP Server Browser
by bytedance
MCP server for browser use access
Runs on your computer★ 39,550Apache-2.0Updated 14 months ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
vibatchium
The browser layer for an always-on box. Many logged-in identities, running unattended, all at once — on real Chrome, with stealth on by default, and with a security model for letting an AI near the credentials.
One daemon, N persistent Chrome sessions, a vb CLI and an MCP server. Self-hosted, free, Apache-2.0.
pipx install 'vibatchium[all]'patchright install chrome vb setup # register the MCP server + agent skill (Claude Code, Codex, Cursor) vb explore https://example.com
Is this for you?
| You want… | Use |
|---|---|
| An agent driving your signed-in browser while you watch | Claude in Chrome, Chrome Auto Browse — first-party, free, better integrated |
| The stealthiest single browser you can buy | CloakBrowser — fingerprints patched in Chromium's C++ (paid for concurrency) |
| The leanest driver for one agent | bladebro — five tools, one Rust binary |
| Browser automation without anti-bot pressure | playwright-mcp, agent-browser — bigger, older, better tested |
| Many accounts on one box, running unattended, against sites that fight automation | vibatchium |
That last row is the whole wedge. Supervised agents hand control back to you at every login wall and CAPTCHA; a library leaves the fleet — sessions, budgets, crash recovery, credentials — for you to build. vibatchium is that fleet layer.
How it compares
As of 2026-10-06, from each project's own README, source and release notes (the MCP-cost row is our own measurement¹). Rows where we lose are included on purpose.
| vibatchium | CloakBrowser | bladebro | agent-browser | playwright-mcp | |
|---|---|---|---|---|---|
| N persistent logged-in sessions at once | yes, free, one daemon | 1 free (latest build) · more on Pro | one Chrome per agent session | yes, one daemon per session | one per profile dir |
| Unattended ops: crash self-heal, leases, budgets, idle freeze, goals | all of them | — | partial (crash relaunch, idle timeout) | partial (idle timeout, restore) | idle timeout |
| Agent can *use* a secret but not *read* it (origin-bound fill, read-back refused, TOTP) | yes | — | — | vault, origin check | --secrets redaction |
| Prompt-injection scanning of page content | yes | — | — | boundary markers (opt-in), no scanning | — |
| Browserless HTTP on the session's own cookies, Chrome TLS fingerprint · keyless web search | yes | — | — | — | — |
| Browser | stock Chrome | own Chromium build | stock Chromium | Chrome for Testing default | stock Chrome |
| Stealth layer | CDP-level (Patchright) | engine-level (87 C++ patches) | CDP-level ("6-layer"), no Runtime.enable | none in core; via cloud providers | none |
| Published stealth score | not yet | 30/30 on its own detector list | 68/80 Stealth Bench V1 (self-run) | — | — |
| MCP startup cost in Claude Code¹ | ~2.7k tokens (89 tools, 5 always loaded) | n/a | ~3.4k tokens (5 tools) | not measured | not measured |
| Platforms | Linux (macOS: CI probe, unsupported) | Linux · macOS · Windows | Linux · macOS · Windows | all | all |
¹ bytes/4 of tools/list plus server instructions, measured over stdio. Clients without tool search load every tool: vb mcp --caps min is 12 tools, ~3.8k tokens. bladebro's own README says ~1.9k.
Where the others are genuinely better: CloakBrowser's engine-level patches go deeper than any CDP-level layer can — and vb start --browser-binary will drive a Chromium build you bring. bladebro has a stealth benchmark number and we don't; until we do, read our stealth claims as measured on scoreboards, below, not on production walls. Both run on more operating systems.
What only vibatchium does
1. A fleet of logged-in identities on one box. Each session is its own Chrome and profile, with its own proxy, timezone and GPU node, and — opt-in with vb persona set — its own screen and window, because by default every headless session on one machine reports the same 800×600 screen. vb fleet-check measures how alike your sessions still look. They run in parallel on one daemon that keeps them alive: a crashed renderer is relaunched on the same profile, parked sessions have their renderers stopped and thawed on the next call, leases stop two agents clobbering one session, and goals give a task a step/spend/time budget that survives a daemon restart.
vb --session alice start && vb --session alice go https://x.com # log in once, stays logged invb --session bob start && vb --session bob go https://x.com vb --session alice act "open notifications" & vb --session bob extract & wait vb fleet-check --sessions alice,bob # how twinned are they?
2. Credentials an agent can use but never see. The vault fills a password or a live TOTP code into the page without the value reaching the model's context, a screenshot or a log — and only into the site it belongs to. Over MCP, a prompt-injected agent can't type your GitHub password into a lookalike page, can't read it back with value or eval while it sits in the field, and can't edit the vault or pull a code. An agent with a *shell* is the operator — the CLI has deliberate escape hatches — so give agents MCP, not Bash, if that boundary matters to you.
printf %s "$GH_PASSWORD" | vb secret set github.com password --stdinprintf %s "$GH_TOTP_SEED" | vb secret set github.com totp-seed --stdin vb --session work fill @e7 --use-secret github.com:password vb --session work fill @e9 --use-secret github.com:totp vb wait-email-code github.com # operator CLI: polls IMAP and prints the code; refused over MCP
3. Page text is treated as untrusted. Every session scans the page text it returns for instructions aimed at the agent and flags them by default; wrap fences them off and redact removes them. Caller-supplied file paths are confined too, so an injected agent can't upload ~/.ssh or write into .git/hooks.
4. A browserless lane on the same identity. vb fetch reuses a session's cookies and proxy with Chrome's TLS fingerprint and client hints — JSON endpoints behind your login at curl speed, and it tells you when it can't match the browser. vb search finds URLs with no API key and no per-session budget.
vb --session work fetch https://api.example.com/v1/mevb search "site reliability postmortem" -n 20 --urls
Status: alpha, active development. 2,331 tests green in CI (Linux, Python 3.11–3.14). Coding agents: read AGENTS.md first — the one-call recipes and the traps worth skipping.
Detector scores quoted below (bot.sannysoft, CreepJS, Cloudflare cold-launch) are manual observations, not CI-asserted — no test in the suite gates on them, and they are only as current as the last hand-run. The generated block under Measured scores is the one to trust.
Install
pipx install vibatchium # core: browse / extract / screenshot / N parallel sessionspipx install 'vibatchium[all]' # + fetch/search lanes, credential vault, VLM read, REST shim
(or pick extras: [fetch], [secrets], [llm], [rest])
patchright install chrome vb setup # register MCP + an auto-discoverable skill (idempotent) vb install # report which optional lanes are available
On a uv venv (no pip), add an extra with uv pip install --python /bin/python curl_cffi. Bleeding edge from master: pipx install 'git+https://github.com/trueoriginlabs/vibatchium#egg=vibatchium[all]'.
Install as a skill / plugin
vb setup wires up the agents on *this* machine. To pull just the agent skill into any agent skills.sh supports (Claude Code, Codex, Cursor, Gemini CLI, Copilot, …), or to install skill + MCP server as one Claude Code plugin:
npx skills add trueoriginlabs/vibatchium # skill only, any agent/plugin marketplace add trueoriginlabs/vibatchium # Claude Code: skill + vb mcp /plugin install vibatchium@vibatchium
Both still need the vb CLI on PATH (pipx install 'vibatchium[all]') — the skill drives it and the plugin's MCP server *is* vb mcp. On Claude Code, pick the plugin or vb setup, not both, or you register the server twice. The skill file is generated from vibatchium/setup_cmd.py; edit there and run python scripts/sync_skill.py.
Quick start
vb explore https://example.com # one call: text-first, auto-closesvb research --target https://example.com \ # parallel fan-out, N intents --intent "pricing model" --intent "customers" --intent "tech stack"
Real Chrome vs fake Chrome
A wave of "headless browser for AI agents" tools rebuild the browser from scratch (Rust + V8, no Blink/Skia) to hit tiny memory and sub-100ms page loads. The catch is structural: with no rendering engine, they can't produce a real device's fingerprint — they synthesize one. And synthetic fingerprints don't hold still.
vibatchium drives *real* Google Chrome, so its fingerprints are real — and, more to the point, stable. The single test that separates the two is fingerprint stability across navigations. Run the same canvas + WebGL probe on two pages in one session:
| vibatchium (real Chrome) | synthesized-fingerprint engines | |
|---|---|---|
| canvas hash, page A → page B | identical | reseeded per navigation |
WebGL readPixels | real, deterministic pixels | often Math.random() |
| WebGL renderer | a real ANGLE renderer¹ | stub / zeros |
¹ Chrome's own software renderer (SwiftShader) by default — still a coherent, deterministic Chrome value, not a stub. A hardware-GPU string (e.g. ANGLE (Intel …)) needs the opt-in --gpu flag.
A real device returns the same fingerprint every page load; a fingerprint keyed off Date.now() does not — and *that inconsistency* is exactly what lie-detection fingerprinters (CreepJS and friends) flag. Measured: vibatchium's canvas hash and WebGL readback are byte-identical across navigations, and CreepJS reported 0 % stealth-tampering (no synthetic-environment signatures) when last run by hand. That figure is not regression-tested — treat it as an observation, not a guarantee.
This is not a claim of invisibility. The moat is fingerprint *authenticity*, not hiding that a browser is automated — vibatchium still reads as headless on the headless-specific tells (see Honest limits), and real-GPU WebGL (--gpu) is opt-in. But real, consistent fingerprints pass the consistency tier that synthetic ones fail *by construction* — and that tier is what stands between you and a login wall.
Multi-session in 10 lines
vb session new workvb --session work start vb --session work go https://github.com # log in by hand once vb session new banking vb --session banking start vb --session banking go https://bank.example.com vb --session work click @e3 & # truly parallel — vb --session banking fill @e5 hi & # separate Chromes, no cookie bleed wait vb session list
Active-session resolution: --session FLAG → $VIBATCHIUM_SESSION env → ~/.config/vibatchium/active-session → default. Cap via VIBATCHIUM_MAX_SESSIONS=8 (default 8).
Multi-agent: shared sessions vs a private daemon
On one s
Only the beginning is shown; read the rest in the repo