WebRun Browser Automation

ai.webrun/webrunVersion 1.0.2

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

Status

Responds496 msNov 14, 2026, 13:35 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 13:35 UTC
Latency: 496 ms
Remotes responding: 1 of 1
Sign-in: API key
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://api.webrun.ai/mcpResponds496 msNov 14, 2026, 13:35 UTC

No sign-in

Claude Code

claude mcp add --transport http webrun https://api.webrun.ai/mcp --header 'Authorization: Bearer <YOUR_TOKEN>'

Replace <YOUR_TOKEN> before running.

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: webrun
Remote MCP server URL: https://api.webrun.ai/mcp
This server expects the header Authorization.

Cursor

{
  "mcpServers": {
    "webrun": {
      "url": "https://api.webrun.ai/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Replace <YOUR_TOKEN> before running.

VS Code

code --add-mcp '{"name":"webrun","type":"http","url":"https://api.webrun.ai/mcp","headers":{"Authorization":"Bearer <YOUR_TOKEN>"}}'

Replace <YOUR_TOKEN> before running.

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

23 tools

Tools of WebRun Browser Automation
	Description		Read-only	Idempotent	Open world
`browser_task`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: only a workflow run carries the workflow's own rules, tracking and memory, so a session run will behave differently. If the user says "run it", "run it once", "test it" or "try it" about a workflow, that means trigger_workflow, not this tool.	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: only a workflow run carries the workflow's own rules, tracking and memory, so a session run will behave differently. If the user says "run it", "run it once", "test it" or "try it" about a workflow, that means trigger_workflow, not this tool.	Yes	No	No	Yes
`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 MODE: omit workflowId and provide name, prompt (a Goal / Ground rules / Stages / Output browsing runbook — see the prompt field description), and a schedule; the connection's environment is used automatically. Ask the user only what it should do and when it should run, in plain language — pick sensible defaults for everything else and state them; never ask about environments or technical settings. Results are delivered to your connected chat and appear in session history.	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 MODE: omit workflowId and provide name, prompt (a Goal / Ground rules / Stages / Output browsing runbook — see the prompt field description), and a schedule; the connection's environment is used automatically. Ask the user only what it should do and when it should run, in plain language — pick sensible defaults for everything else and state them; never ask about environments or technical settings. Results are delivered to your connected chat and appear in session history.	No	No	No	No
`create_session`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, tracking and memory, so a session run will behave differently.	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, tracking and memory, so a session run will behave differently.	Yes	No	No	Yes
`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 browsing runbook following the Goal / Ground rules / Stages / Output contract in the promptTemplate field description. For tasks that must handle each new item exactly once (new messages, forward once, skip seen), memoryContract is REQUIRED — three plain-English fields addressed to the agent: groundRules, memoryInstruction and itemIdentity (see the field descriptions); the platform wires the tracking itself — never write memory or tracking steps into the prompt. Created in the connection's environment automatically — omit environmentId and never ask the user to choose one. Write the user's concrete values (names, URLs, numbers) directly into the prompt; use {{variables}} ONLY when the user explicitly wants a reusable template with per-run inputs. Everything else is optional and defaults sensibly — do not quiz the user about settings. A supplied schedule is stored as a setting only — the workflow does not run on a timer until deployed via create_agent. To run or TEST the workflow, use trigger_workflow ONLY — never browser_task or create_session.	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 browsing runbook following the Goal / Ground rules / Stages / Output contract in the promptTemplate field description. For tasks that must handle each new item exactly once (new messages, forward once, skip seen), memoryContract is REQUIRED — three plain-English fields addressed to the agent: groundRules, memoryInstruction and itemIdentity (see the field descriptions); the platform wires the tracking itself — never write memory or tracking steps into the prompt. Created in the connection's environment automatically — omit environmentId and never ask the user to choose one. Write the user's concrete values (names, URLs, numbers) directly into the prompt; use {{variables}} ONLY when the user explicitly wants a reusable template with per-run inputs. Everything else is optional and defaults sensibly — do not quiz the user about settings. A supplied schedule is stored as a setting only — the workflow does not run on a timer until deployed via create_agent. To run or TEST the workflow, use trigger_workflow ONLY — never browser_task or create_session.	No	No	No	No
`get_task_status`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.	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.	No	Yes	Yes	Yes
`get_work_list`Page through the work list a workflow keeps between runs. Each item comes with its band: on a watch list failing, unreadable, changed_today or watching; on a collect list needs_approval, new_today, handled or seen. Identify the workflow by workflowId or exact title; filter by band or a search query; pass nextCursor back as cursor for the next page. Read-only.	Page through the work list a workflow keeps between runs. Each item comes with its band: on a watch list failing, unreadable, changed_today or watching; on a collect list needs_approval, new_today, handled or seen. Identify the workflow by workflowId or exact title; filter by band or a search query; pass nextCursor back as cursor for the next page. Read-only.	No	Yes	Yes	No
`get_workflow`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, any pending logins, and a summary of its work list when it keeps one (for a typed list: its bands, counts and newest or watched items — page it with get_work_list). Identify by workflowId or exact title. Read-only; proxy credentials are masked.	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, any pending logins, and a summary of its work list when it keeps one (for a typed list: its bands, counts and newest or watched items — page it with get_work_list). Identify by workflowId or exact title. Read-only; proxy credentials are masked.	No	Yes	Yes	No
`guardrail_response`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.	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.	Yes	No	No	Yes
`list_agents`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.	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.	No	Yes	Yes	No
`list_environments`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 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.	No	Yes	Yes	No
`list_sessions`List all active browser sessions for this account. Read-only.	List all active browser sessions for this account. Read-only.	No	Yes	Yes	No
`list_workflows`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.	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.	No	Yes	Yes	No
`pause_agent`Pause an active scheduled agent — it stops firing until resumed. Get agentId from list_agents.	Pause an active scheduled agent — it stops firing until resumed. Get agentId from list_agents.	Yes	No	No	No
`pause_session_task`Pause the task currently running in a browser session. Resume it later with resume_session_task.	Pause the task currently running in a browser session. Resume it later with resume_session_task.	Yes	No	Yes	Yes
`resume_agent`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).	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).	Yes	No	No	No
`resume_session_task`Resume a previously paused task in a browser session.	Resume a previously paused task in a browser session.	Yes	No	Yes	Yes
`screenshot`Capture a screenshot of the current browser page in an active session. Returns the screenshot as an inline image. Read-only.	Capture a screenshot of the current browser page in an active session. Returns the screenshot as an inline image. Read-only.	No	Yes	Yes	Yes
`send_task`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.	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.	Yes	No	No	Yes
`stop_session_task`Cancel the task currently running in a browser session, keeping the session alive for new tasks.	Cancel the task currently running in a browser session, keeping the session alive for new tasks.	Yes	No	Yes	Yes
`terminate_session`End a browser session and free its resources. The session and any running task cannot be resumed afterwards.	End a browser session and free its resources. The session and any running task cannot be resumed afterwards.	Yes	No	Yes	Yes
`trigger_workflow`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, and submit data on third-party websites as the workflow's prompt requires. Pass values for the workflow's {{variables}} in `variables` (stored variableValues defaults fill any gaps). Returns a sessionId — poll get_task_status for the result.	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, and submit data on third-party websites as the workflow's prompt requires. Pass values for the workflow's {{variables}} in `variables` (stored variableValues defaults fill any gaps). Returns a sessionId — poll get_task_status for the result.	Yes	No	No	Yes
`update_work_list`Change the work list a workflow keeps between runs. op: add (items; on a watch list, new watched items), remove (items; on a watch list, stop watching them), mark_handled or unmark (items), skip_approval (drafts waiting for approval), clear (empty the list; keepHandled keeps handled items on a collect list; a watch list keeps its watched items and drops their readings). Confirm with the user before remove or clear. Refused while a run of this workflow is in progress. To change what the list records, use update_workflow.	Change the work list a workflow keeps between runs. op: add (items; on a watch list, new watched items), remove (items; on a watch list, stop watching them), mark_handled or unmark (items), skip_approval (drafts waiting for approval), clear (empty the list; keepHandled keeps handled items on a collect list; a watch list keeps its watched items and drops their readings). Confirm with the user before remove or clear. Refused while a run of this workflow is in progress. To change what the list records, use update_workflow.	Yes	No	No	No
`update_workflow`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. promptTemplate follows the same Goal / Ground rules / Stages / Output runbook contract as create_workflow (see that field's description). memoryContract is the exception to whole-replace: supplying its three fields updates them while platform tracking details are preserved. On a workflow that keeps a typed list: an outputSchema change needs workList keep or empty (ask the user); listType and queue mode can't change; a different result type goes through resultType, previewed first and applied once the user confirms.	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. promptTemplate follows the same Goal / Ground rules / Stages / Output runbook contract as create_workflow (see that field's description). memoryContract is the exception to whole-replace: supplying its three fields updates them while platform tracking details are preserved. On a workflow that keeps a typed list: an outputSchema change needs workList keep or empty (ask the user); listType and queue mode can't change; a different result type goes through resultType, previewed first and applied once the user confirms.	Yes	No	Yes	No

Details

Registry status: Active
Published: Aug 8, 2026
Updated: Aug 8, 2026
Website: https://webrun.ai/⁠ (opens in a new tab)
Repository: Not given
Categories (suggested): Browser automationSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing