WebRun Browser Automation MCP server

What does WebRun Browser Automation need from you?

Bearer token — WebRun API key as a bearer token.

• AuthorizationrequiredsecretHTTP header

  WebRun API key as a bearer token.

What tools does WebRun Browser Automation expose? (21)

Read from the live server. Click any tool for its input schema.

• 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 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_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 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_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 connection's environment automatically — you rarely need this tool for those, and should not ask the user to choose an environment.
• 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; pass scope "all" for every environment. Read-only.
• 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, and any pending logins. Identify by workflowId or exact title. Read-only; proxy credentials are masked.
• 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; 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_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 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_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. 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_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, 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_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 scope "all" for every environment. Read-only.
• 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).

What the code can do

This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

• No source repository — This registry entry does not link to a public repo, so its code cannot be reviewed before you install it.

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

• Maintenance30%not measurable

  No commit history available.

• Adoption20%not measurable

  No usage data available.

• Transparency20%25%

  1/4: ✗ public source repo, ✗ declared license, ✗ documentation, ✓ discoverable tool list.

• Provenance15%0%

  No source repository to trace the code back to.

• Packaging15%100%

  Remote endpoint with documented authentication.

Maintain WebRun Browser Automation? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

[![WebRun Browser Automation on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/ai-webrun-webrun)](https://mcp-skills-hub.vercel.app/mcps/ai-webrun-webrun)