snapshot_page
pruned, indexed tree of interactive/labelled/text-bearing elements, each with a ref, role, accessible name and box; narrow it with viewportOnly, roles or maxElements
How to use it
snapshot_page is exposed by the Mobius MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the snapshot_page tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.
Install Mobius MCP
claude mcp add mobius-mcp -- npx -y mobius-mcpOther tools in Mobius MCP (19)
, captureaccessibilitytree: markup and the full accessibility tree, for markup/ARIA questions rather than finding something to click
, hover, typetext, presskey, scrollto, scrollby, selectoption, setcheckbox: trusted CDP input events, each moving the on-page cursor overlay with its own icon
arbitrary JS in the tab, fully open, with no read-only enforcement
HAR 1.2 with full request/response bodies; anything missed inline is re-fetched over CDP (binary bodies base64-encoded)
locate elements by natural-language description ("accept cookies button"); returns ranked refs plus totalMatched
, setactivetab, getcapturesettings: which tabs are streaming, which one is active, and which event categories a tab is capturing (so an empty result is distinguishable from "that category is off")
, getjobresult, canceljob: manage a long-running job (profiling, recording) started by another tool
request/response headers plus size-capped, redacted bodies for text-like content types (no CDP needed)
, getrecenterrors, getlogssince, clearlogs
, getrequestbody: CDP fallback for the rare body capture that gets skipped (binary, oversized, non-text)
every open tab, not just enabled ones
connection health check and remediation guidance
, switchtab, reloadtab: browser control
, enablecapture: start a capture session without a toolbar click
many steps against one tab in a single round trip, stopping at the first failure and returning what completed; find/snapshotpage/takescreenshot are eligible steps, with screenshots returned interleaved in step order
, startmemoryprofile: job-based; check progress with getjobstatus/getjobresult/canceljob
, enddebugsession: one ordered timeline of console, network, navigation and DOM events instead of correlating snapshots by hand (single-tab, doesn't survive a full-page navigation)
, capturefullpage, captureelement
, waitfornavigation, waitforrequest, waitforelement: block with a timeout instead of polling in a loop