Actions

Actions

Every action is an MCP tool and an HTTP endpoint with the same parameters. A test fails the build if one exists without the other.

Browser actions

Everything you can do to a page.

Tool	Endpoint	Does
open_session	POST /browser/open	Start a browser session. Do this first.
navigate	POST /browser/navigate	Go to a URL. Returns the resulting URL and page title.
interact	POST /browser/interact	Perform a mouse action on an element.
write	POST /browser/write	Type text into an input, textarea or contenteditable.
press_key	POST /browser/press-key	Press a named key, at an element or wherever focus currently is.
extract	POST /browser/extract	Read an element's visible text and innerHTML.
screenshot	POST /browser/screenshot	Capture a PNG of the page and return it as an image you can see.
save_pdf	POST /browser/pdf	Print the current page to PDF and keep it with the session's files.
execute_script	POST /browser/script	Run JavaScript in the page and return its result.
frame	POST /browser/frame	Move into an iframe, or back out of it.
dialog	POST /browser/dialog	Answer a native alert, confirm or prompt dialog.
resize	POST /browser/resize	Resize the browser window.
upload_file	POST /browser/upload	Attach a file to a file input.
end_browser	POST /browser/end	Quit the browser and free its Grid slot. Do this when finished.

Flows

A sequence of the actions above, saved under a name and run in one call. See Flows for what a flow document looks like.

Tool	Endpoint	Does
list_flows	POST /flows/list	Every flow this session can run.
get_flow	POST /flows/get	One saved flow, with its steps.
flow_schema	POST /flows/schema	The shape of a flow document.
save_flow	POST /flows/save	Create or replace a flow.
run_flow	POST /flows/run	Run a saved flow.
delete_flow	POST /flows/delete	Delete one of this session's flows.

Files

What a session has produced, and how to keep one past the browser that made it. See Files.

Tool	Endpoint	Does
session_files	POST /files/list	Every file this session has.
keep_file	POST /files/keep	Keep one download beyond its browser.

Over HTTP session_id is always required. Over MCP it depends on whether the server can identify you — see Sessions.

---

Installing · Deployment · Administration