agent-remote-browser
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
agent-remote-browser

Give an AI agent a real browser, without giving it your machine or your passwords.
agent-remote-browser is a remote MCP server. An agent (a Notion Custom Agent, Claude, any MCP client) connects to it and drives a Chromium that runs on your server: open a page, read it, click, fill a form, sign in to a site. Each agent works in its own browser profile, a sandboxed container that keeps its cookies between sessions and can reach only the domains you allowed.
You stay in control from a small admin UI on localhost: create profiles, choose their domains, save logins, grant or revoke agent access, and watch (or take over) any browser live.
Quick start
Requires Docker.
cp .env.example .env # on macOS: ALLOW_NO_SANDBOX=1 (no gVisor)
mkdir -m 700 secrets && head -c 32 /dev/urandom > secrets/login_key # once
openssl rand -base64 48 | tr -d '\n' > secrets/better_auth_secret && chmod 600 secrets/* # once
docker compose up -d --build # MCP on http://localhost:18787/mcp, admin on http://localhost:18788
docker compose exec gateway node src/cli.ts admin create you@example.com # once: password, then TOTPThen open the admin UI, create a profile with its allowed domains, and connect your agent to http://localhost:18787/mcp (OAuth) or create an API key for it. Use the exact origin set in PUBLIC_URL: OAuth binds tokens to it.
Related MCP server: MultiZen MCP Server
How it works
flowchart LR
agent["🤖 AI agent<br/>Notion, Claude, MCP Jam…"]
you["🧑 Admin<br/>browser on localhost"]
subgraph host["Your server (Docker)"]
direction LR
subgraph gateway["gateway · no Docker socket"]
mcp["MCP endpoint /mcp<br/>OAuth 2.1 · API keys"]
ui["Admin UI :18788<br/>password + TOTP"]
db[("arb.db<br/>hashed tokens<br/>encrypted logins")]
proxy["Egress proxy<br/>one per profile<br/>domain allowlist"]
end
runner["runner<br/>only service with<br/>the Docker socket<br/>no network"]
subgraph computers["one container per profile"]
c1["Chromium + agent-browser<br/>no network · no caps<br/>read-only · gVisor"]
end
end
web(("🌐 Allowed<br/>websites"))
agent -- "HTTPS<br/>tunnel or reverse proxy" --> mcp
you --> ui
mcp --- db
ui --- db
mcp -- "fixed ops only<br/>ensure · exec · stop" --> runner
ui --> runner
runner -- "Docker Engine API" --> c1
c1 -- "unix socket" --> proxy
proxy -- "public IPs only" --> webThe life of one tool call, say click:
The agent calls
POST /mcpwith its token. The gateway checks the token (stored as a hash), its scope (one profile, orglobal) and the kill switch, then writes an audit line.The gateway asks the runner to run a fixed
agent-browsercommand in that profile's container. The runner is the only piece that can touch Docker, and it accepts a short list of operations, never a free command line.The browser acts. Any request it makes leaves through the profile's egress proxy, which lets through only the allowed domains and refuses private IPs.
The result goes back to the agent. Page text is wrapped in
<untrusted_page_content>, so the agent knows not to follow instructions found on a page.
What you get
Isolation by default. Each profile is its own container: no network, every capability dropped, read-only root filesystem, gVisor runtime. The only way out is the allowlisted proxy.
Logins the agent never sees. Saved passwords are encrypted (AES-256-GCM, key kept outside the database). The agent's
logintool asks the gateway to type them; the password never enters the agent's context, the admin page or a command line.Standard agent auth. OAuth 2.1 (dynamic client registration or CIMD, PKCE) for MCP clients that support it, API keys with a mandatory expiry for the others. You pick the scope on the consent page.
Leases. A
globalagent can borrow a profile for a while (1 to 120 minutes, sliding); meanwhile no one else drives it.Human in the loop. Live view of every browser, with a takeover mode to click and type yourself, and fill a saved login on screen.
Agent asks for help. Stuck on a captcha or a 2FA code, the agent calls
request_humanand gets a link for its user; its browser pauses until you take over and click Done. While an agent holds a lease, the live view is watch-only unless you take its request.Ops basics included. Prometheus
/metrics, JSON logs, an audit file, restic backups, a runbook, CI with an end-to-end smoke on gVisor.
Tools exposed to the agent
Tool | What it does |
| Go to a URL (allowed domains only) |
| Accessibility tree of the page, with element refs to act on |
| Visible text of the page or of one element |
| Click or fill an element from the snapshot (never a password: see |
| Press a key (Enter, Tab, Escape…) |
| Previous page |
| PNG of the viewport |
| Sign in to a site with a saved login, typed by the server |
| Hand the browser to a human (captcha, 2FA, consent) and wait for the outcome |
|
|
|
|
A token scoped to profile:<id> drives that profile only. A global token drives a profile through a lease, passed to every browser tool.
Development
Requires Node >= 24 (target runtime: Node 26). TypeScript runs as-is, no build step.
npm ci
npm test # unit + integration on an in-memory fake driver, no Docker needed (< 1 s)
npm run typecheck
npm run smoke # end to end against a fresh stackLearn more
deploy/runbook.md: running it on a server (secrets, tunnel or reverse proxy, agents, backups, upgrades, uninstall).
docs/reference.md: deploy settings, CI, metrics, code layout, gateway and runner, database, auth details, admin API, login key, operator commands.
SECURITY.md: open security topics and residual risks.
Status: early, built for a single operator running their own stack. Expect breaking changes between commits; there are no versioned releases yet.
License
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Browz hosted MCP (free public beta): let an AI app drive your own Browz browser profiles from anywhere. Connect https://mcp.gobrowz.com/mcp and sign in with your Browz account (OAuth) or an agent token. Each call is relayed to the Browz app on your computer, which must be online with Remote control on and have a hardware security chip (Mac Secure Enclave or TPM 2.0). 17 tools: profiles, tabs, navigate, snapshot, act, wait, screenshot. Cookies, downloads and stored sign-ins stay on your computer.
Real Chrome for coding agents over MCP: browse, replay playbooks, human takeover, HIPAA & BAA.
Cloud browsers for AI agents: get past bot detection, sign in with MFA, run web tasks at scale.
A real cloud browser for your AI agent. Connect Claude, ChatGPT, Cursor or any MCP client: the agent opens, reads and acts on pages with real mouse and keyboard input, in an isolated session on Browser.lol's servers. You watch live and take over at any time, for example to sign in. Sessions in other countries, an Anonymous Mail inbox for sign-up codes and saved profiles. OAuth sign-in or an API key; needs the Premium plan.
Related MCP Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and human operators to drive isolated, persistent browser profiles with their own cookies, fingerprints, and proxies. Exposes tools for profile lifecycle, navigation, clicking, typing, extraction, screenshots, JavaScript evaluation, tabs, cookies, and waits over a local MCP endpoint.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and human operators to drive isolated browser profiles with persistent cookies, fingerprints, and proxies, exposing navigation, clicking, typing, extraction, screenshots, JS evaluation, tabs, cookies, and waits to MCP clients.-
- FlicenseNot gradedqualityAmaintenanceExposes a local MCP endpoint that lets AI agents and human operators drive isolated Chromium profiles — each with its own cookies, fingerprint, and proxy — through tools for navigation, clicking, typing, extraction, screenshots, JS evaluation, tabs, and cookie management. Persistent per-profile session state keeps logins and context alive across launches and across AI sessions, so agents can complete real authenticated workflows.-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and human operators to drive isolated, persistent browser profiles over MCP, including navigation, clicking, typing, extraction, screenshots, tab and cookie management, and raw CDP calls. Each profile keeps its own cookies, login state, fingerprint, and proxy, so authenticated workflows and sessions carry over between runs.MIT