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.
Description from the maker (original English)
Browser MCP: the app under test egresses via the real ISP while the agent stays on the VPN.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
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": {
"lan-direct": {
"command": "npx",
"args": [
"-y",
"lan-direct",
"browser"
]
}
}
}Run this in your terminal
claude mcp add lan-direct -- npx -y lan-direct browserPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"lan-direct": {
"command": "npx",
"args": [
"-y",
"lan-direct",
"browser"
]
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"lan-direct": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"lan-direct",
"browser"
]
}
}
}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.
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account farshadmomo, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed –, and the latest version (1.0.2) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser
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
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.
Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.
MCP server for browser use access
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.
A skill and a browser MCP for coding agents behind a full-tunnel VPN — Claude Code and Codex.
Your VPN has to stay on, because that's how the agent reaches its API. But the app you're testing calls services that reject the VPN's foreign exit IP: a domestic API, a payment or SMS gateway, a bank endpoint. Turning the VPN off isn't an option — it cuts the agent off.
lan-direct gives the app an ISP-direct path while the agent stays on the tunnel. No admin, no routing-table edits, no VPN reconfiguration. How it works.
Requires Node ≥ 20.6, plus PowerShell on Windows or bash and curl on Linux/macOS. No admin, no symlinks, no renaming.
npm install -g lan-direct
lan-direct install-skill # or --codex claude mcp add playwright-split --scope user "--" npx -y lan-direct browser
Then restart the agent. That's it — the same three lines on every platform.
npx -y lan-direct browser is the better MCP command however you install: it survives the checkout moving, which an absolute path into a clone does not.
Why `"--"` is quoted. On Windows
clauderesolves toclaude.ps1, and PowerShell's
parameter binder strips a bare
--before the script ever sees it. The CLI then reads-y
as one of its own flags and fails with
error: unknown option '-y'. Quoting protects it,
and quotes are a no-op in bash — so the same line works in PowerShell, bash and cmd.
Prefer this if you want to edit the skill or track it — one git pull updates everything, where npm needs npm update -g lan-direct && lan-direct install-skill because install-skill copies files rather than linking them.
Either way, your own host list at ~/.lan-direct-hosts is never touched.
1. Clone into your agent's skills directory. Both agents discover skills by scanning a directory for SKILL.md — they just scan different ones.
# Windows - Claude Code
git clone https://github.com/farshadmomo/lan-direct.git "$HOME\.claude\skills\lan-direct"
New-Item -ItemType Directory -Force -Path "$HOME\.agents\skills" | Out-Null git clone https://github.com/farshadmomo/lan-direct.git "$HOME\.agents\skills\lan-direct"
# Linux / macOS - Claude Code
git clone https://github.com/farshadmomo/lan-direct.git ~/.claude/skills/lan-direct
mkdir -p ~/.agents/skills git clone https://github.com/farshadmomo/lan-direct.git ~/.agents/skills/lan-direct
2. Register the browser MCP:
powershell -NoProfile -ExecutionPolicy Bypass `
-File "$HOME\.claude\skills\lan-direct\scripts\install.ps1"
The installer verifies the bypass actually works, registers the server against this checkout, and prints the equivalent ~/.codex/config.toml block for Codex. Safe to re-run — it replaces the existing entry rather than duplicating it.
On Linux/macOS there's no installer script; register it directly:
claude mcp add playwright-split --scope user "--" \
node ~/.claude/skills/lan-direct/scripts/lan-browser.mjs --port 8900
Restart the agent. Then /lan-direct in Claude Code, or in either agent just describe the problem — the description frontmatter is the trigger, firing on phrasings like "test this while my VPN is on" or "the API rejects the VPN IP".
To update: git -C pull. No reinstall needed.
Using both agents from a single clone
Clone once, then link the second location. On Windows a junction works without admin or Developer Mode, unlike a symlink:
git clone https://github.com/farshadmomo/lan-direct.git "$HOME\.claude\skills\lan-direct"
New-Item -ItemType Directory -Force -Path "$HOME\.agents\skills" | Out-Null cmd /c mklink /J "$env:USERPROFILE\.agents\skills\lan-direct" "$env:USERPROFILE\.claude\skills\lan-direct"
macOS/Linux:
git clone https://github.com/farshadmomo/lan-direct.git ~/.claude/skills/lan-direct
mkdir -p ~/.agents/skills ln -s ~/.claude/skills/lan-direct ~/.agents/skills/lan-direct
One git pull then updates both.
Installing somewhere else (for editing the skill)
Clone wherever you like and link it in. A junction needs no admin; a symlink needs an elevated shell or Developer Mode:
git clone https://github.com/farshadmomo/lan-direct.git "D:\projects\lan-direct"
cmd /c mklink /J "$env:USERPROFILE\.claude\skills\lan-direct" "D:\projects\lan-direct"
However you install it, the directory inside the skills folder must be named lan-direct — both agents discover by directory name, and it has to match name: in SKILL.md.
Rules live in lan-hosts.txt and are suffix matches:
.ir every .ir host
digikala.com also seller.digikala.com, api.digikala.com, ...
Anything not matched takes the tunnel. List domestic hosts only — adding a foreign one sends it out through an ISP that may filter it.
The shipped list covers .ir wholesale plus the Iranian services that live on other TLDs: payment (zarinpal, payping, nextpay), SMS/OTP (kavenegar, melipayamak, farazsms, ippanel), hosting (parspack, hostiran, mizbanfa), maps (neshan), commerce (digikala, torob, basalam), education and jobs (quera, faradars, maktabkhooneh, 7learn, irantalent), AI (hoosha, gapgpt), and the analytics domains those sites embed (najva, yektanet). Every one was checked: all are unreachable over the tunnel and respond over the ISP.
Put them in `~/.lan-direct-hosts`, one per line, same format:
# my own
aparat.com internal.corp
That file is never touched by git pull, and is read each time the browser starts — no reinstall, no restart of anything but the browser. Rules from all three sources merge: shipped file, your file, and any --lan-hosts a,b passed at launch.
Getting a rule wrong fails in a way that looks like the site being down, so the proxy prints the route it chose for every connection. Check that before blaming the site — or ask directly, without starting anything:
$ lan-direct route hoosha.com youtube.com api.anthropic.com
24 rules in effect
hoosha.com lan ISP (bound) youtube.com vpn tunnel api.anthropic.com vpn tunnel
Two halves, installed together:
| What it does | |
|---|---|
The skill (SKILL.md) | Teaches the agent the whole workflow — detect, verify, pick a mechanism per stack, tear down. Discovered automatically by scanning for SKILL.md. |
The browser MCP (lan-browser.mjs) | A Playwright MCP server that starts and owns its own proxy, and routes per host: domestic sites via the ISP, everything else via the tunnel, in one browser session. |
The MCP is what makes browsing work at all — Chromium has no source-binding flag, so a browser can only reach the ISP through a proxy. Without it the skill covers backends and CLIs but not pages.
Per-socket source-address binding. A socket explicitly bound to the physical adapter's IP takes that adapter's default route instead of the tunnel's:
$ curl -s https://api.ipify.org # 203.0.113.7 (VPN exit)
$ curl -s --interface 192.168.1.20 https://api.ipify.org # 198.51.100.42 (real ISP)
No admin rights, no routing-table edits, no VPN reconfiguration, nothing global. Because it's per-socket it is opt-in by construction — a process that doesn't ask for it *cannot* be affected. That's the property that keeps the agent on the tunnel.
This is deliberately not route add. A static route is global: it would pull every process off the tunnel for that destination, the agent included, and it needs admin.
A server process has no --interface flag, so there are two ways to give it one:
| Your backend | Mechanism |
|---|---|
| Node / Next.js | lan-bind.mjs — a --import preload that binds every socket in the process |
| Everything else | lan-proxy.mjs — a local proxy whose *outbound* sockets are bound, driven by HTTP_PROXY |
If your backend is Node, `HTTP_PROXY` will not work and will fail silently.
Native fetch runs on Node's built-in undici, which ignores proxy environment variables on Node ≤ 23 and accepts no https.Agent. Verified on Node 22.20: plain env vars, NODE_USE_ENV_PROXY=1, and --use-env-proxy all do nothing — the proxy log stays empty while traffic goes out over the VPN. This hits Next.js, the openai SDK, and anything else on native fetch.
lan-bind.mjs patches net/tls in a preload, which reaches the bundled undici. That covers native fetch, the openai SDK, axios, node-fetch, got and plain http/https at once — no dependency, no proxy process, no HTTP_PROXY. NODE_OPTIONS propagates to forked workers, so it covers Next.js and Vite dev servers.
It skips loopback destinations on purpose: a socket sourced from the LAN IP cannot reach 127.0.0.1, so without that guard any app with a local Redis/Postgres/Mongo would die on EADDRNOTAVAIL.
All paths below use $skill for wherever you installed it:
$skill = "$HOME\.claude\skills\lan-direct" # Claude Code
$skill = "$HOME\.agents\skills\lan-direct" # Codex
1. Detect and verify. Exits 0 only if the bypass actually works.
powershell -NoProfile -ExecutionPolicy Bypass -File "$skill\scripts\lan-detect.ps1"
bash ~/.claude/skills/lan-direct/scripts/lan-detect.sh # Linux / macOS
Emits lanIp, gateway, lanDns, subnet, tunnelActive, vpnAdapter, directEgress, lanEgress, fakeIpDns, bypassWorks. It probes twice and compares, rather than assuming — and refuses to proceed if the bypass doesn't hold, so you never get a false pass.
2a. Node backend. Copy-paste as-is; only lanIp needs filling in:
$env:LAN_BIND = "<lanIp>"
$env:NODE_OPTIONS = "--import file:///$($skill -replace '\\','/')/scripts/lan-bind.mjs" npm run dev
Same thing from Git Bash, with the path written out:
LAN_BIND=<lanIp> \
NODE_OPTIONS="--import file:///C:/Users/YOU/.claude/skills/lan-direct/scripts/lan-bind.mjs" \ npm run dev
--import needs an absolute file:// URL with forward slashes on Windows — a bare Windows path fails.
2b. Anything else. Start the proxy:
node "$skill\scripts\lan-proxy.mjs" --bind <lanIp> --self-test # run with the tunnel UP
node "$skill\scripts\lan-proxy.mjs" --bind --port 8899
Then launch the backend with HTTP_PROXY=http://127.0.0.1:8899, HTTPS_PROXY=http://127.0.0.1:8899, NO_PROXY=localhost,127.0.0.1, .
See SKILL.md for stacks where HTTP_PROXY still isn't enough — notably PHP under Apache, where the service doesn't inherit your shell and libcurl never sees the variables.
Neither path is a superset of the other. Measured on an Iranian ISP behind a foreign tunnel:
| via VPN | via ISP | |
|---|---|---|
| youtube, x, facebook, telegram, reddit | work | dead |
| hoosha, neshan, avalai | dead | work |
| github, google, npm | work | work |
| api.anthropic.com | works | 403 |
That last row is why the agent must never be moved off the tunnel — do it and the agent stops working entirely.
The browser MCP handles the mix in one session. Chrome is told to send *everything* to the proxy and makes no routing decision itself; the proxy reads th
Only the beginning is shown; read the rest in the repo