WebRun Browser Automation

by webrun.ai · ai.webrun/webrun

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

OnlineRemote
Category
Browser automation
Connection
Remote (HTTP)
Tools
23 reported
Status
Online

Connect it to your AI

Claude Code

claude mcp add --transport http webrun https://api.webrun.ai/mcp

Claude, ChatGPT, Cursor and other apps

Add it as a custom connector with this URL (Streamable HTTP):

https://api.webrun.ai/mcp

This server expects extra headers, usually an API key from its maker.

Cursor, VS Code and other apps (mcp.json)

{
  "mcpServers": {
    "webrun": {
      "url": "https://api.webrun.ai/mcp"
    }
  }
}

Tools it offers

23 tools, as the server itself reported during our check on Oct 31, 2026.

  • browser_taskExecute 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 workfl
  • create_sessionCreate 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
  • send_taskSend 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_taskPause the task currently running in a browser session. Resume it later with resume_session_task.
  • resume_session_taskResume a previously paused task in a browser session.
  • stop_session_taskCancel the task currently running in a browser session, keeping the session alive for new tasks.
  • terminate_sessionEnd a browser session and free its resources. The session and any running task cannot be resumed afterwards.
  • guardrail_responseRespond 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_statusCheck 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.
  • screenshotCapture a screenshot of the current browser page in an active session. Returns the screenshot as an inline image. Read-only.
  • list_sessionsList all active browser sessions for this account. Read-only.
  • list_environmentsList 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 connecti
  • list_workflowsList 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; p
  • get_workflowFull 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 sum
  • get_work_listPage 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. Ident
  • create_workflowCreate 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
  • update_workflowUpdate 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
  • update_work_listChange 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
  • trigger_workflowRun 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
  • create_agentCreate 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, starti
  • list_agentsList 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 scop
  • pause_agentPause an active scheduled agent — it stops firing until resumed. Get agentId from list_agents.
  • resume_agentResume 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).

Questions

What is the WebRun Browser Automation MCP server?

Run multi-step tasks in a real Chrome browser: persistent environments, live view, human takeover. It is made by webrun.ai and listed in the official MCP Registry as ai.webrun/webrun. MCP (Model Context Protocol) is the open standard that lets AI apps like Claude, ChatGPT and Cursor use outside tools.

How do I add WebRun Browser Automation to Claude?

In the Claude app or claude.ai, open Settings, then Connectors, choose "Add custom connector" and paste https://api.webrun.ai/mcp. In Claude Code, run: claude mcp add --transport http webrun https://api.webrun.ai/mcp

How do I add WebRun Browser Automation to ChatGPT?

ChatGPT can use remote MCP servers as connectors. In ChatGPT settings, under Apps and Connectors, turn on developer mode if asked, create a new connector and paste https://api.webrun.ai/mcp.

How do I add WebRun Browser Automation to Cursor?

Open Cursor settings, go to MCP, choose "Add new MCP server" (or edit ~/.cursor/mcp.json) and add: { "mcpServers": { "webrun": { "url": "https://api.webrun.ai/mcp" } } }

Does WebRun Browser Automation work right now?

Yes. It responded when we last checked on 31 Oct 2026. We check remote MCP servers every day.

What can WebRun Browser Automation do?

It gives your AI 23 tools, including browser_task, create_session, send_task, pause_session_task, resume_session_task. The full list is on this page.

Is this your server? Get the badge for your README
chen.media/mcp badge

Markdown (GitHub README)

[![Listed on chen.media/mcp](https://chen.media/mcp/badge/ai-webrun-webrun.svg)](https://chen.media/mcp/ai-webrun-webrun)

HTML (switches to dark mode on its own)

<a href="https://chen.media/mcp/ai-webrun-webrun"><picture><source media="(prefers-color-scheme: dark)" srcset="https://chen.media/mcp/badge/ai-webrun-webrun.svg?theme=dark"><img src="https://chen.media/mcp/badge/ai-webrun-webrun.svg" alt="Listed on chen.media/mcp" height="40"></picture></a>

More in Browser automation

See all