MCP server Page automation · Pro

Drive a page without switching on the signal that names a bot

Mosaic reads and drives pages for the REST API and MCP without enabling CDP’s Runtime domain, the switch Playwright flips. Clicks and keys go through the same human-input path as the warm-up robot.

0calls to Runtime.enable anywhere in the app
1attachment per tab, held open so refs survive between calls
Driving a Mosaic profile from Playwright: start it over the local API and attach to its DevTools socket
The API screen’s Automation tab: start a profile over the local API and attach Playwright, or let Mosaic drive the page itself.
01 How it works

Page automation, step by step

Snapshot the page

An isolated world reads the page and hands out refs for what can be clicked or typed into.

Act by ref

Click, type or press against a ref. A stale ref is refused rather than silently landing somewhere else.

Move like a hand

The cursor keeps its place between actions and travels to the target; keys are typed with human timing, never set with a value.

02 Inside it

The smaller things it does

Why not Playwright

Enabling Runtime was measured flipping a public detector to “bot”. Every domain this uses was measured clean on a real profile first.

No scroll without a wheel

Mosaic does not scroll an element into view by script before a click; it scrolls with a wheel, as a person would.

Limit

An isolated world does not see the page’s own uncaught errors. Reading them needs a wrapper the page can see, and the tool that turns it on says so.

Next Try it on your own accounts

Page automation is part of Pro

Try Pro free for 14 days, then $49 a month for any number of profiles. Cancel before day 14 and you pay nothing.