A headless browser
- Fresh profile, so every site is logged out
- Two-factor prompts nobody is there to answer
- Trips bot detection precisely because it is one
- Runs somewhere you cannot see it
Optional integration
The side panel does not need it. Browsentic Bridge also serves MCP, so Claude Code, Codex, Cursor or Zed can drive the same signed-in browser.
claude mcp add browsentic -- browsentic mcp
Headless or signed in
It has no session, no cookies and no two-factor state, so most useful pages sit behind a login. Browsentic works in the tab you are already signed in to.
How it is built
Browsentic Bridge speaks MCP over stdio, so any MCP client can drive the same signed-in browser. Several can at once, because one Bridge owns the browser link.
Tool definitions are generated from the same registry the extension is built from, so an MCP client is never offered a tool the browser cannot run.
A module under src/lib/actions/page/ and one line in the registry. It is published as an MCP tool in the same change.
Clients
Browsentic Bridge owns the browser link, so several clients drive the same browser at once. Every step surfaces on the side panel timeline, marked external.
One difference
An MCP client gets every page tool except the live scripting pair. A script runs only after a person reads its source in the panel and approves it, and that approval cannot carry over to a client outside the conversation. Everything else is identical, because both come from the same registry.
Resources
browsentic://page/diagram
Layout diagram with stable selectors
browsentic://page/current
Structured snapshot of the active tab
browsentic://page/text
Rendered text, as a reader would see it
Free and open source under Apache 2.0, with no API key, subscription or account. One line installs Browsentic Bridge and opens the extension’s store page. Nothing connects until you pair the two.