Repository navigation
get_site_data
One site's saved cookies and storage.
| MCP resource | workspace://site-data/{site} |
| HTTP | GET /site-data/{site} |
One site's saved data: its cookies, and the localStorage and sessionStorage of each of its origins. An httpOnly cookie's value is shown as •••; nothing else is hidden. The site is a host from the workspace://site-data listing.
| Name | Type | Required | Default | Notes |
|---|---|---|---|---|
site |
string | yes | — | A host from the listing, such as app.example.com. |
Every call names its workspace: an X-Workspace header, or
?workspace=<name>. Sending both is refused. See Workspaces.
| Field | Type | Notes |
|---|---|---|
site |
string | |
uri |
string | |
cookies |
array | |
storage |
array | Per origin: the same host on another port or scheme is another origin. sessionStorage is the one tab's, for the page the save was made on. |
own_cookies |
array | Cookies this site owns (host or .host): what Forget removes. |
kept_shared |
array | Parent-domain cookies it only sits under: Forget keeps them. |
| Status | Means |
|---|---|
400 |
No workspace named, two names given, or no saved data for that site. Do not retry it unchanged. |
401 |
Missing or wrong bearer token. |
500 |
Something failed that this server did not expect. |
Over MCP the same failures arrive as a tool error.
MCP
read workspace://site-data/{site}
read_resource(uri="workspace://site-data/{site}")
HTTP
curl -X GET $SELENIUM_FLOW/site-data/{site} \
-H "Authorization: Bearer $TOKEN" \
-H "X-Workspace: $WORKSPACE"The action pages are generated from openapi.yaml, which is itself generated from the live MCP tool schemas — so they describe the server that shipped, not the one someone remembered. Prose belongs in wiki-notes/<tool>.md in the repo.
selenium-flow · MIT
Start here
Guides
Lifecycle
Going places
Doing things
Getting things out
Site data
Console and network