browsentic://page/diagram
Layout diagram with stable selectors
Capabilities
41 page tools: sense a page,
act on it, and wait it out
Perceiving the page as structure rather than pixels: a layout diagram, stable selectors, rendered text, screenshots. Listening while you talk it through. Sensing progress and waiting out an upload or a deploy so you never have to hover over it, or working to a clock when the page offers nothing to watch. Then acting with a human hand, and remembering enough to run the whole thing again unprompted. Aim by CSS selector, visible text, ARIA role or index, because visible text outlives the redesigns that break selectors. Or hand it the lens and point at the thing yourself.
Read · 10 tools
Sense the page before touching it
Takes in the page as structure rather than pixels: a snapshot carrying a layout diagram and stable selectors, rendered text, patient waiting for an element to appear or vanish, the search control wherever a site hid it, a capture of the whole tab or one element, the palette and luminance a page actually paints, a WCAG contrast score, and the captcha hiding inside a closed shadow root. When it cannot name the thing you mean, it hands you the lens and you point at it.
Act · 14 tools
Reach into the page with a human hand
Reaches into the page with a human hand. Pointing, hovering, dragging, focusing, filling inputs and contenteditables, streaming text in keystroke by keystroke at a human pace, choosing an option, selecting a passage, pressing keys with modifiers, committing a form, clicking with a genuine browser-level gesture where a synthetic one is refused, ticking a captcha checkbox, and retheming a page on its own terms.
Navigate · 6 tools
Find its own way around the site
Finds its own way around. Opening a URL, retracing back and forward, reloading, searching a site on its own terms rather than guessing at query strings, scrolling to whatever matters, spawning a tab, surveying the ones you already have open, closing the ones it is finished with.
Wait · 7 tools
Sit through the slow part for you
Senses the progress signals a page gives off, then keeps watch in the background while an upload, a build or a deploy runs its course: the tab stays pinned, percent and ETA are tracked, and an MCP client can long-poll until it lands. When a page offers nothing to watch, it works to a clock instead, waking itself in ten minutes or every two to redo the check and tell you only what changed.
Files · 2 tools
Hand a file to the form asking for it
Reaches for the files you keep in Browsentic and hands one to a file input on the page, so an upload flow stops waiting on a human at the file picker.
Recordings · 2 tools
Replay a job you showed it once
Recalls the sessions you recorded and replays them as ordered, deliberate steps, re-checking every target against the live page before it commits to acting.
Zero tool calls
Three read-only resources
Page context an MCP client can read directly, without spending a tool call on it.
browsentic://page/current
Structured snapshot of the active tab
browsentic://page/text
Rendered text, as a reader would see it
Aiming
Four ways to name the thing you mean
Most tools that touch an element take the same target object. Visible text outlives the redesigns that break CSS selectors, so prefer it where you can. Where nothing describes it, hand over the lens and point at it yourself.
selector
A CSS selector, ideally one page_getPageInfo handed back rather than one you guessed.
text
Case-insensitive visible text the element should contain. The most durable of the four.
role
A tag name or ARIA role, to narrow the matches down.
nth
A zero-based index, for when several elements legitimately match.
Stop describing the page. Hand it over.
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