agent-browser MCP server
io.github.AetherAI3 · Updated
Self-hosted Chrome for AI agents, with a live noVNC view a human can take over.
At a glance
agent-browser is an MCP server in the Dev Tools & Git category. It runs locally over stdio via `npx -y aether-browser mcp`, and needs AGENT_BROWSER_CONTROLLER_TOKEN and AGENT_BROWSER_OBSERVER_TOKEN. It scores A (82/100) on the MCP Skills Hub health score as of Oct 28, 2026.
One-click install
Opens your editor and pre-fills the config. Your editor will ask before adding it.
How to install agent-browser in your AI client
Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.
How to install agent-browser in Claude CodeAnthropic's agentic CLI
Add the server
bashclaude mcp add agent-browser -e 'AGENT_BROWSER_CONTROLLER_TOKEN=<AGENT_BROWSER_CONTROLLER_TOKEN>' -e 'AGENT_BROWSER_OBSERVER_TOKEN=<AGENT_BROWSER_OBSERVER_TOKEN>' -- npx -y aether-browser mcpFill in your credentials
Replace <AGENT_BROWSER_CONTROLLER_TOKEN>, <AGENT_BROWSER_OBSERVER_TOKEN> with your real values. Keep secrets out of any config file you commit.
Verify it's connected
bashclaude mcp listSharing it with your team?
Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).
Use it in a session
Ask Claude to use the tools this server exposes. It discovers them automatically.
How to install agent-browser in Claude DesktopDesktop app (MCP config)
Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json
Add this server
json{ "mcpServers": { "agent-browser": { "command": "npx", "args": [ "-y", "aether-browser", "mcp" ], "env": { "AGENT_BROWSER_CONTROLLER_TOKEN": "<AGENT_BROWSER_CONTROLLER_TOKEN>", "AGENT_BROWSER_OBSERVER_TOKEN": "<AGENT_BROWSER_OBSERVER_TOKEN>" } } } }Fill in your credentials
Replace <AGENT_BROWSER_CONTROLLER_TOKEN>, <AGENT_BROWSER_OBSERVER_TOKEN> with your real values. Keep secrets out of any config file you commit.
Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.
How to install agent-browser in CursorAI-first code editor
Create / edit .cursor/mcp.json in your project
json{ "mcpServers": { "agent-browser": { "command": "npx", "args": [ "-y", "aether-browser", "mcp" ], "env": { "AGENT_BROWSER_CONTROLLER_TOKEN": "<AGENT_BROWSER_CONTROLLER_TOKEN>", "AGENT_BROWSER_OBSERVER_TOKEN": "<AGENT_BROWSER_OBSERVER_TOKEN>" } } } }Fill in your credentials
Replace <AGENT_BROWSER_CONTROLLER_TOKEN>, <AGENT_BROWSER_OBSERVER_TOKEN> with your real values. Keep secrets out of any config file you commit.
Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.
How to install agent-browser in Codex CLIOpenAI coding agent
Add to ~/.codex/config.toml
toml[mcp_servers.agent-browser] command = "npx" args = ["-y", "aether-browser", "mcp"] env = { AGENT_BROWSER_CONTROLLER_TOKEN = "<AGENT_BROWSER_CONTROLLER_TOKEN>", AGENT_BROWSER_OBSERVER_TOKEN = "<AGENT_BROWSER_OBSERVER_TOKEN>" }Fill in your credentials
Replace <AGENT_BROWSER_CONTROLLER_TOKEN>, <AGENT_BROWSER_OBSERVER_TOKEN> with your real values. Keep secrets out of any config file you commit.
Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.
How to install agent-browser in WindsurfCodeium's agentic IDE
Edit ~/.codeium/windsurf/mcp_config.json
json{ "mcpServers": { "agent-browser": { "command": "npx", "args": [ "-y", "aether-browser", "mcp" ], "env": { "AGENT_BROWSER_CONTROLLER_TOKEN": "<AGENT_BROWSER_CONTROLLER_TOKEN>", "AGENT_BROWSER_OBSERVER_TOKEN": "<AGENT_BROWSER_OBSERVER_TOKEN>" } } } }Fill in your credentials
Replace <AGENT_BROWSER_CONTROLLER_TOKEN>, <AGENT_BROWSER_OBSERVER_TOKEN> with your real values. Keep secrets out of any config file you commit.
Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.
How to install agent-browser in ClineVS Code autonomous agent
Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.
Add the server
json{ "mcpServers": { "agent-browser": { "command": "npx", "args": [ "-y", "aether-browser", "mcp" ], "env": { "AGENT_BROWSER_CONTROLLER_TOKEN": "<AGENT_BROWSER_CONTROLLER_TOKEN>", "AGENT_BROWSER_OBSERVER_TOKEN": "<AGENT_BROWSER_OBSERVER_TOKEN>" } } } }Fill in your credentials
Replace <AGENT_BROWSER_CONTROLLER_TOKEN>, <AGENT_BROWSER_OBSERVER_TOKEN> with your real values. Keep secrets out of any config file you commit.
How to install agent-browser in VS CodeCopilot / MCP support
Create .vscode/mcp.json
json{ "servers": { "agent-browser": { "type": "stdio", "command": "npx", "args": [ "-y", "aether-browser", "mcp" ], "env": { "AGENT_BROWSER_CONTROLLER_TOKEN": "<AGENT_BROWSER_CONTROLLER_TOKEN>", "AGENT_BROWSER_OBSERVER_TOKEN": "<AGENT_BROWSER_OBSERVER_TOKEN>" } } } }Fill in your credentials
Replace <AGENT_BROWSER_CONTROLLER_TOKEN>, <AGENT_BROWSER_OBSERVER_TOKEN> with your real values. Keep secrets out of any config file you commit.
Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.
What does agent-browser need from you?
API key — Controller token, if the server runs authenticated.
AGENT_BROWSER_URLoptionalEnvironment variableBase URL of your Agent Browser server. Defaults to http://127.0.0.1:8092.
AGENT_BROWSER_CONTROLLER_TOKENoptionalsecretEnvironment variableController token, if the server runs authenticated.
AGENT_BROWSER_OBSERVER_TOKENoptionalsecretEnvironment variableObserver token for read-only health and snapshot calls.
AGENT_BROWSER_URLoptionalEnvironment variableBase URL of your Agent Browser server. Defaults to http://127.0.0.1:8092.
AGENT_BROWSER_CONTROLLER_TOKENoptionalsecretEnvironment variableController token, if the server runs authenticated.
AGENT_BROWSER_OBSERVER_TOKENoptionalsecretEnvironment variableObserver token for read-only health and snapshot calls.
Pass secrets through your shell environment rather than committing them into a config file.
What tools does agent-browser expose?
This server runs as a local package. We only query remote servers for their tool list — asking this one would mean executing it, so its tools are listed in the documentation below.
What the code can do
Read from the published package source — never executed. Parsed 3 of 3 source files.
This server can run other programs on your machine, read and write files and read your environment variables.
How it was published
- Has a provenance attestation tying this artifact to the commit it was built from.
- 1 npm maintainer — a single point of compromise · last published by ather-ai-llc.
Maintainer of this package and think something here is wrong? Tell us and we'll correct it.
Before you install
Signals gathered from the source repo and package registry — not a safety verdict.
What it can reach
- Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
- Downloads at launch — The package is fetched from its registry each run unless you pin a version.
- Last commit 1 day ago — Actively maintained.
- 14 GitHub stars — Community adoption signal.
- 31 weekly downloads — Very few installs — you would be an early user.
Client compatibility
Health score
A · 82Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated
- Maintenance30%100%
Last commit 1 day ago.
- Adoption20%35%
14 stars, 31 weekly downloads.
- Transparency20%75%
3/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✗ discoverable tool list.
- Provenance15%100%
Package and registry entry point at the same repository.
- Packaging15%100%
Publishes a pinned version (0.2.2).
Documentation
Full READMEAgent Browser See what your agent sees.
Self-hosted Chrome for AI agents. Your agent drives one real browser session — and you can watch it happen, and step in.
Quickstart · API · MCP · Security model · Node client · Python client · Contributing · Changelog
<sub> An 18-second recorded demonstration. The agent signs in, reaches a 2FA prompt it has no way to answer, and stops. A human types the code into <strong>the displayed session</strong>, then the agent continues. Capture provenance, checksums, and independently verifiable limits are documented. · How this was recorded </sub>
Why this exists
Most browser tooling for agents hands the model a browser you cannot see. When it misreads a page or stalls on a login, all you get is a transcript and a guess.
Agent Browser runs one headed Chrome session. Your agent drives it through a small JSON API, and a live view of that same session sits open in front of you. When the agent gets stuck, you take over in the window it is already using — then hand it back.
Start the runtime:
docker compose up --buildThen reach it however you like:
npm install aether-browser # TypeScript
pip install aether-browser # Python
claude mcp add agent-browser -- npx -y aether-browser mcp # any MCP clientQuickstart
Excerpt — the full document is on GitHub.
Alternatives to agent-browser
- Agent360 Browser MCPA · 92Drive your real, logged-in Chrome from any AI agent - 40 tools. Needs our Chrome extension too.
- Vibe Test — Browser Testing AgentA · 88Code-aware browser testing agent — 14 Playwright tools for AI code editors via MCP
- Agent GuildB · 79See and steer Claude Code, Codex, Antigravity, Grok, Docker Agent and shell sessions in Agent Guild.
- agent-tools (x402 + MCP + A2A directory)B · 78Discover x402 services, MCP servers and A2A agents by intent — agent-tools.cloud directory.
Maintain agent-browser? Add a badge to your README
Shows its health grade, and links readers to install steps for every client.
[](https://mcp-skills-hub.vercel.app/mcps/io-github-aetherai3-agent-browser)Catalog data refreshed . Something wrong? Report it.