Next-Generation Browser Control
for AI Assistants
Give Claude Code, Cursor, Gemini/Antigravity, Windsurf, and VS Code direct control of your live, authenticated Chrome and Brave browser sessions. 43 tools, sub-4ms cold startup, ~3.8MB RAM, and zero headless login barriers.
Instant Client Setup
Connect your assistant directly to your daily browser in 60 seconds with copy-paste configs.
{
"mcpServers": {
"browser-control": {
"command": "browser-mcp"
}
}
}
~/.browser-mcp/extension (or run browser-mcp install to unpack automatically).Interactive Architecture
Click any layer to inspect protocol guarantees, security boundaries, and telemetry specifications.
AI Coding Assistant
Claude Code, Cursor, Gemini, Windsurf, or VS Code client.
stdio JSON-RPC 2.0Native Rust Core
Standalone binary engine with sub-4ms boot and ~3.8MB RAM.
Port 9876-9895Autonomous Token Shield
Semantic DOM pruning, monotonic [e1] handles, and local spooling.
Origin VerifiedLive Chrome & Brave
Authenticated user tabs, CDP compositor overlays, and multi-session isolation.
Persistent MV2Real-World Automation Scenarios
Inspect how Browser Control handles both everyday user tasks and advanced developer workflows.
Interactive Tool Directory
Explore all 43 native browser tools covering both everyday user automation and high-intensity developer workflows.
Autonomous Token Shield
Eliminate LLM context bloat and rate-limit penalties with intelligent local pruning.
Semantic & Viewport DOM Pruning
Raw webpage DOMs routinely surpass 300,000 tokens. Token Shield condenses pages into an accessible semantic tree, pruning off-screen nodes and mapping elements to monotonic handles ([e1]-[e43]).
- 98.8% Token Savings: 142k tokens distilled to 1.6k
- Spatial Viewport Pruning:
viewport_only=truesaves 50–70% - Handle Generation: Instant targeting with
[e1]refs
Atomic Form Batching & Spooling
Rather than burning one LLM turn per input field, Browser Control dispatches entire forms atomically with event-loop pacing, with automatic disk spooling for massive payloads.
- Single-Turn Batching: Fill 20+ fields in one request
- Event-Loop Pacing: 35ms debounced React/Vue events
- Disk Spooling: Payloads >2,500 tokens stored locally
Production Proven in Real Browsers
No dummy simulations. See how Browser Control operates inside live browser tabs.
Multi-Session Tab Groups
Color-coded tab groups isolate independent AI agent conversations without profile locks.
Human-in-the-Loop Safeguards
Sensitive 2FA prompts, SMS OTPs, and CAPTCHAs pause cleanly for human completion.
43 Automation Tools
Hardware clicks, atomic form batching, cookie extraction, and failed network telemetry.
Engineered Without Compromise
How Browser Control compares to legacy Node.js bridges and headless runners.
| Capability | Browser Control (Native Rust) | Agent360 (Legacy Node) | Playwright MCP | BrowserMCP.io |
|---|---|---|---|---|
| Runtime Engine | Standalone Native Rust (0 dependencies) | Node.js runtime (npm dependency) | Node.js + Headless Chromium | Node.js runtime (npm dependency) |
| Startup Latency | < 3.8 ms (instant native binary) | ~450 ms (Node cold start) | ~2,500 ms (Chromium boot) | ~500 ms |
| Memory Footprint | ~3.8 MB RAM | ~85 MB RAM | ~350 MB+ RAM | ~90 MB RAM |
| Context Token Shield | Built-in (spooling >2.5k tokens + handles) | None (dumps raw DOM) | None (35,000+ raw tokens) | None |
| Spatial Viewport Pruning | Yes (viewport_only=true, 50-70% savings) | No | No | No |
| Atomic Form Batching | Yes (single-turn multi-field fill) | No (1 field per turn) | No (sequential actions) | No |
| Authenticated Session Reuse | Yes (active Brave/Chrome tabs) | Yes (Chrome tabs) | No (isolated profile default) | Yes (Chrome tabs) |
| Diagnostics & Overlays | browser_highlight + failed requests | Screenshot only | Trace viewer file | Screenshot only |
| Tool count | 43 | 41 | 73 | Not published |
| Multi-Session Concurrency | 20 concurrent sessions | 20 concurrent sessions | Single session (profile lock) | Single session |
| Telemetry & License | MIT · Zero Telemetry | MIT · Zero Telemetry | Apache-2.0 · Microsoft Telemetry | MIT · Unmaintained |
Frequently Asked Questions
Everything you need to know about architecture, privacy, and client support.
What is Browser Control and why was it rewritten in Rust?
How does Browser Control differ from Playwright MCP and headless runners?
Is my browsing data and token security protected?
127.0.0.1:9876-9895). It enforces strict Origin: chrome-extension://[a-p]{32} verification on incoming WebSockets to prevent unauthorized local process connections. Source code is completely open and auditable on GitHub.How does 2FA assistance and CAPTCHA solving work?
browser_ask_user to render an interactive in-browser dialog. The automation pauses cleanly until you approve or complete the step on your own screen, after which the agent resumes in the exact same tab.Which AI coding assistants are supported?
browser-mcp install to automatically configure all detected client configuration files.Who authors and maintains this project?
Take Full Control of Your Real Browser
Install Browser Control in 60 seconds and give your AI assistant access to authenticated web sessions.