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
MCP server
Claude Code, Codex, Antigravity, Cursor, Zed: anything fluent in MCP takes the wheel of the same real tab. Headless automation wakes up with amnesia, no session, no cookies, no two-factor state, and a login wall between it and anything worth doing. Browsentic inherits the tab you are already signed into.
claude mcp add browsentic -- browsentic-mcp
The difference that matters
No session, no cookies, no two-factor state, and a login wall between it and anything worth doing. Browsentic inherits the tab you are already signed into.
How it is built
The daemon speaks MCP over stdio, so Claude Code, Codex, Antigravity or anything else that speaks the protocol drives the same real, logged-in browser. Several at once, because one daemon owns the link.
Tool definitions are generated from the same registry the extension ships. A tool that describes something the browser cannot do is not a bug you can write. It is a build that does not exist.
A module under lib/actions/page/ plus one line in the registry, and it publishes as an MCP tool at the same time. No second place to remember.
Clients
One daemon owns the browser link, so several clients can drive the same browser at once. Every step they take surfaces on the side panel timeline, marked external.
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 MIT licensed. Nothing to sign up for, no key to paste, and a fresh install connects to nothing until you redeem a pairing code yourself.
claude mcp add browsentic -- browsentic-mcp