Built on Google's DevTools MCP

1browser for AI agents

Give your coding agent control of real, persistent browser profiles — with their own fingerprint and proxy — not disposable sessions that vanish when the task ends.

View on GitHub Quick start

Not a custom protocol —  a fork of Google's own

onebrowser-mcp is a fork of ChromeDevTools/chrome-devtools-mcp, extended with 1browser's own CDP methods for profiles, fingerprints, proxies and auth. You get everything the official Chrome DevTools MCP does — network inspection, performance tracing, memory snapshots, Lighthouse audits — plus persistent, identity-aware profiles on top.

Works with the agent you already use

No lock-in to one assistant. Any MCP-compatible client connects the same way.

Why "profile" beats "context" for agents

Default browser automation gives agents a browser context — think incognito. Close it, and identity, cookies and login state disappear. Fine for a one-off task, unusable for anything that needs to run reliably over days or weeks.

Browser context (default)

No ID, no persistence, resets on close

1browser profile

Has an ID, persists, reusable across agent runs

Quick start

{ 
     "mcpServers": {
          "onebrowser-devtools": {
              "command": "npx",
              "args": ["-y", "@the1browser/
onebrowser-mcp@latest"]
         } 
    }
}