Browserr AI Browser Engine
Top AI Tools

Browserr AI Browser Engine

Visit website

Browserr is a free, open-source, MCP-first browser engine for AI agents in one 120 MB Rust binary, with 42 tools, evidence logs, and a…

Browserr AI Browser Engine

Browserr is a browser engine built for AI agents, and it takes a deliberately different path from the Chromium wrappers that dominate agent tooling. It is a single Rust binary of about 120 MB, built on the Servo engine and the SpiderMonkey JavaScript engine, and it exposes the browser through the Model Context Protocol instead of the Chrome DevTools Protocol. The project appeared on Hacker News on 14 November 2026, and its pitch is aimed at developers who have watched agents hang on a page, hallucinate a click, or quietly fail without leaving a trace.

A Browser Engine Built for Agents

Most agent browsers are Chromium with a remote control layer bolted on, which means the agent inherits a protocol of more than a thousand CDP endpoints and a footprint of hundreds of megabytes. Browserr replaces that with its own engine and a protocol small enough to audit in an afternoon: 42 MCP tools and 22 commands, speaking JSON over a loopback socket, with zero CDP endpoints. The engine runs on Windows, Linux, and macOS, with CPU rendering by default and a GPU option, and it handles React 18 and Vue 3, IndexedDB, Web Animations, WebGL through ANGLE, and single page applications.

The Protocol in Brief

The Browserr protocol is organized around a handful of verbs that cover what an agent actually needs to do on a page. Reading comes first: read_page returns the prose of a page, while read_structure returns every element with its rectangle and selector, and form fields carry their label, constraints, state, and validity. Interaction uses act, with click_element and set_value sending real pointer events and React and Vue safe writes. Form filling happens in one round trip with type aware writes, and submitting a form runs the page own validation, then reports the resulting URL, any alerts, and any invalid fields.

Fail Closed by Design

Three commitments shape Browserr, and the site states them plainly: it blocks when unsure, it hands the page to a human when a human is needed, and it leaves evidence for everything it did. Requests can be held for an allow, deny, or respond decision, and an unanswered request is denied after five seconds. Missing credentials fail closed instead of being silently skipped, and authentication and file picker events are surfaced to the agent rather than swallowed. The evidence layer records every fetch in a network ring buffer, keeps an append only action log, takes screenshots on demand, and puts a confirm gate on payment submits. Access is token gated, so unauthenticated sockets get nothing, not even events.

Browserr in the Terminal

One of the more surprising features is browserr-term, which renders real pages inside a terminal pane at native resolution using Sixel or Kitty graphics, with a working fallback for every terminal. It works inside tmux, and it uses the same binary and the same evidence layer as the MCP server, so nothing extra needs to be installed. That makes Browserr usable in places a headed browser cannot go, such as a remote server over SSH, and it gives developers a way to watch what their agent is doing without leaving the terminal.

Pricing and Getting Started

Browserr is free and open source, with no account and no telemetry, as stated on the official Browserr site. There are no paid tiers to compare, which keeps the decision simple: download the binary for your platform, or add the MCP server to any MCP capable agent with one configuration block. The PyPI package browserr-mcp lets MCP clients fetch and verify the engine by SHA256 on first run, with later starts instant. Windows, Linux x64 and ARM64, and macOS on Apple Silicon are supported, with the Linux ARM64 build covering the Raspberry Pi 4 and 5. The site notes that CAPTCHA support still depends on Servo compatibility.

KEEP EXPLORING

More tools to discover.

Find your next starting point