WebRun Browser Automation

ai.webrun/webrun

Run multi-step tasks in a real Chrome browser: persistent environments, live view, human takeover.

Yes, your AI can use this right now.Answered a live MCP handshake in 440 ms with no sign-in needed and exposes 21 tools.

Connect it

Settings → Connectors → Add custom connector
URL: https://api.webrun.ai/mcp

21 tools, verified live

Pulled straight from the server with tools/list on 2026-10-17.
browser_taskcan modify

Execute a browser automation task in a real Chrome browser running in a WebRun cloud environment (docs.webrun.ai). Creates a session, runs the task, and auto-terminates. Best for simple one-off tasks that no saved workflow covers. May navigate, fill forms, and submit data on third-party websites as the task requires. Do NOT use this to run or test a saved workflow — use trigger_workflow instead: o

create_sessioncan modify

Create a persistent session in a real Chrome browser running in a WebRun cloud environment (docs.webrun.ai), for multi-step interactive work. Returns a sessionId for subsequent commands. With an initial task the browser may act on third-party websites immediately. Do NOT use this to run or test a saved workflow — use trigger_workflow instead: only a workflow run carries the workflow's own rules, t

send_taskcan modify

Send a new task to an existing browser session (from create_session). The real Chrome browser may navigate, fill forms, and submit data on third-party websites as the task requires.

pause_session_taskcan modify

Pause the task currently running in a browser session. Resume it later with resume_session_task.

resume_session_taskcan modify

Resume a previously paused task in a browser session.

stop_session_taskcan modify

Cancel the task currently running in a browser session, keeping the session alive for new tasks.

terminate_sessioncan modify

End a browser session and free its resources. The session and any running task cannot be resumed afterwards.

guardrail_responsecan modify

Respond to a guardrail trigger when the browser agent needs human input (credentials, clarification, approval). The response is handed to the live agent, which continues acting on it.

get_task_statusread-only

Check the status of a task previously started in a browser session. Use to poll for completion or detect guardrails. Read-only: reports on the task without affecting it.

screenshotread-only

Capture a screenshot of the current browser page in an active session. Returns the screenshot as an inline image. Read-only.

list_sessionsread-only

List all active browser sessions for this account. Read-only.

list_environmentsread-only

List available browser environments (persistent profiles) for this account. Returns environment IDs needed for persistent sessions in browser_task or create_session. Read-only. NOTE: workflows and agents use the connection's environment automatically — you rarely need this tool for those, and should not ask the user to choose an environment.

list_workflowsread-only

List the user's saved workflows (prompt-templated browser automations, docs.webrun.ai). Shows each workflow's title, schedule, {{variables}}, and run stats. Scoped to the bound environment when this connection has one; pass scope "all" for every environment. Read-only.

get_workflowread-only

Full detail of one workflow: prompt template, {{variables}} and their defaults, trigger + schedule, run settings (starting URL, timezone, model, proxy, output contract, files), memory state, and any pending logins. Identify by workflowId or exact title. Read-only; proxy credentials are masked.

create_workflow

Create a new saved workflow. READINESS BAR: if you could not execute the prompt yourself as a human in a browser — which site, which records, which fields, delivered where, matched to each recipient how — it is not ready; first collect the missing business facts from the user (see the TASK INTERVIEW in the server instructions), then create. Requires title and promptTemplate — write the prompt as a

update_workflowcan modify

Update an existing workflow. Supply workflowId plus only the fields to change: prompt, trigger, schedule, run settings, variables, presentation. Object and array fields are replaced whole; pass null to clear an optional field. Renaming via title keeps the slug stable. The stored schedule stays a saved setting — scheduled agents already deployed from this workflow keep their own timing. promptTempl

trigger_workflowcan modify

Run a workflow now in its deployed environment. This is the ONLY correct way to run or TEST a saved workflow — a run started here carries the workflow's rules, tracking and memory; browser_task/create_session runs do not. When the user says "run it", "run it once", "test it" or "try it" about a workflow, this is the tool they mean. Drives a real Chrome browser: the run may navigate, fill forms, an

create_agent

Create a scheduled agent — a recurring or one-time automation that runs on a timer in a real Chrome browser. Two modes. WORKFLOW MODE: pass workflowId plus a schedule — the platform copies everything else (prompt, starting URL, output contract, model, proxy, policy, files) from the workflow and bakes your variables into the prompt; results and memory stay centralised on the workflow. STANDALONE MO

list_agentsread-only

List the account's scheduled agents (cron deployments): schedule, status, next/last run, and whether each is standalone or deployed from a workflow. Scoped to the bound environment when this connection has one; pass scope "all" for every environment. Read-only.

pause_agentcan modify

Pause an active scheduled agent — it stops firing until resumed. Get agentId from list_agents.

resume_agentcan modify

Resume a paused scheduled agent — recomputes its next run and reactivates it. A completed work-list agent restarts with a fresh full pass. Refuses if the agent's expiry has passed (extend it on the dashboard first).

Alternatives in Browser & Scraping

Compare →
Try “Notion”, “Stripe”, “create invoice”, “browser”