Browser MCP: the app under test egresses via the real ISP while the agent stays on the VPN.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Not yet automatically verified
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
Manual Client & Custom JSON ConfigExpand JSON ▾
Client Config & Setup
Choose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Documentation Overview
lan-direct
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.
Install
Requires Node ≥ 20.6, plus PowerShell on Windows or bash and curl on Linux/macOS. No
admin, no symlinks, no renaming.
From npm
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 Windowsclauderesolves toclaude.ps1, and PowerShell's parameter binder strips a bare--before the script ever sees it. The CLI then reads-yas one of its own flags and fails witherror: unknown option '-y'. Quoting protects it, and quotes are a no-op in bash — so the same line works in PowerShell, bash and cmd.
From a clone
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.
2. Register the browser MCP:
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:
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 <that directory> 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:
macOS/Linux:
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:
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.
Which hosts go via the ISP
Rules live in lan-hosts.txt and are suffix matches:
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.
Adding your own
Put them in ~/.lan-direct-hosts, one per line, same format:
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:
What's in the box
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.
How it works
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:
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 |
The Node trap
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.
Manual use
All paths below use $skill for wherever you installed it:
1. Detect and verify. Exits 0 only if the bypass actually works.
Related MCP Servers
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Lan Direct
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/lan-direct)HTML Embed
<a href="https://allmcps.com/mcp/lan-direct"><img src="https://allmcps.com/api/badge/lan-direct?style=directory" alt="Lan Direct on AllMCPs" /></a>