The open browser for AI agents

Letyouragentsreachthewholeweb.

An open browser bridge for the agents you already use. Your tabs, your logins, your context — already in place.

Chrome extension

macOS Apple Silicon · Chrome 120+ · Node 20+

Speed

3.4× faster

Native fast.

BrowserCtrl142ms
Headless Chrome480ms
Cloud browser1.4s

median action latency, p50

Your real Chrome

signed in

Logged in to 47 sites.

Same profile, cookies, extensions you use daily.

google.comgithub.comlinear.appnotion.so+ 43 more
MCP · driving Chrome

Trust

0 cloud calls.

Every action signed and hash-chained, on your machine.

  • navigate9f3a…b21c
  • click21cd…7a9e
  • submit4f02…ab18
tamper-evident

What you get

Built like infrastructure.

Step 01 · of 04Identity

Your real Chrome.

Not a sandbox, not a headless browser. Your profile, your cookies, your extensions — already logged in to the sites your agent needs.

  • Your existing logged-in sessions
  • Cookies, extensions, settings preserved
  • No fresh auth flows for the agent
shell

$browserctrl status

✓47 sites authenticated

✓ready for agent

47

Sites

14

Extensions

3

Tabs

How it works

Your agent. Your daemon. Your Chrome.

Three components, all on your machine. Wired together by MCP and Native Messaging — no network round-trips, no third-party broker.

AGENT

01 · MCP client

Your AI agent

Claude Code, Cursor, Windsurf — anything that speaks MCP. Sends tool calls over stdio.

MCP

02 · Local daemon

BrowserCtrl daemon

Translates tool calls, manages sessions, persists traces, enforces policy.

CHROME

03 · Real Chrome

Your browser

Your profile, your cookies, your extensions. Driven via CDP through Native Messaging.

Install

Three steps. Two minutes.

Local-first by design. Install the CLI, start the daemon, pair the extension — and your agents can drive Chrome.

STEP 01

Install the CLI

One command, global install. Ships the daemon and MCP server with it.

  • $ npm i -g browserctrl
  • ✓ resolving dependencies
  • ✓ installing browserctrl@0.4.1
  • ✓ linking → /usr/local/bin
  • ok · ready in 1.2s
$ npm i -g browserctrl
STEP 02

Start the daemon

Boots the local MCP server. Leave it running in a terminal — no cloud, no telemetry.

  • $ browserctrl init
  • → starting daemon
  • ✓ listening on 127.0.0.1:7842
  • ✓ MCP server ready
  • ● waiting for extension…
daemon live · waiting
$ browserctrl init
STEP 03

Install the Chrome extension

Pairs your real Chrome with the daemon over Native Messaging.

chromewebstore.google.com

BrowserCtrl

4.1 ★ · v0.4.1

Added to Chrome
Open Chrome Web Store

macOS Apple Silicon · Chrome 120+ · Node 20+

Works with

The agents you already use.

One install. Add the BrowserCtrl MCP server to your editor and start driving Chrome from inside it.

Claude Code

First-party MCP. Add a single entry to your config.

MCP↗

Cursor

Settings → MCP → paste the BrowserCtrl block.

MCP↗

Windsurf

Built-in MCP support since the first release.

MCP↗

Zed

Agent panel reads your local MCP servers directly.

MCP↗

Plus Cline, Continue, Goose, Aider — anywhere MCP runs.