-
Notifications
You must be signed in to change notification settings - Fork 0
navigate
Kelly Ferrone edited this page Sep 16, 2026
·
8 revisions
Go to a URL. Returns the URL and title the browser ended on.
| MCP tool | navigate |
| HTTP | POST /browser/navigate |
Every other action also takes url, and navigates there first only if the browser is somewhere else, so you rarely need this as a separate call.
| Name | Type | Required | Default |
|---|---|---|---|
url |
string | yes | — |
Every call names its session: an X-Session-Key header, or ?session=<name>.
Sending both is refused. See Sessions.
| Field | Type | Notes |
|---|---|---|
url |
string | Current URL after the action. |
title |
string | Page title after the action. |
| Status | Means |
|---|---|
400 |
The request cannot succeed as sent — a missing field, a value that was rejected, or a locator that matched nothing before the wait ran out. Do not retry it unchanged. |
401 |
Missing or wrong bearer token. |
404 |
No such browser session. It ended, the Grid reaped it, or the id was never real. Open a new one and retry. |
500 |
Something failed that this server did not expect. |
503 |
The Grid could not serve this — unreachable, or no free slot for a new browser. Worth retrying after a wait. |
Over MCP the same failures arrive as a tool error.
MCP
navigate(url="…")
HTTP
curl -X POST $SELENIUM_FLOW/browser/navigate \
-H "Authorization: Bearer $TOKEN" \
-H "X-Session-Key: $SESSION" \
-H 'Content-Type: application/json' \
-d '{
"url": "…"
}'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