List your agent

WebRun Browser Automation

MCP server● Hosted · onlinev1.0.2

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

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: fill web forms automatically.
All AI agents to fill web forms automatically, ranked →

Similar tools

Listed for the same task: fill web forms automatically

Reviews

No review yet. Used WebRun Browser Automation? Be the first to help others choose.

What it does

WebRun Browser Automation is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: browser automation. That makes it a candidate for tasks such as fill web forms automatically or test web applications.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.0.2
PriceNot in the registry
First seen26 Sept 2026
Last checked10h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2d ago (live check)

Hosted endpoint

  • https://api.webrun.ai/mcp streamable-http

Required: Authorization (get it from the publisher)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "webrun-browser-automation": {
      "url": "https://api.webrun.ai/mcp",
      "headers": {
        "Authorization": "<your Authorization>"
      }
    }
  }
}

Replace the values in <angle brackets>.

Live check

Electra Index connected to the hosted endpoint 2d ago

ONLINE WebRun Browser Automation answered an MCP connection on 13 Nov 2026 and introduced itself as webrun 2.0.0 (MCP protocol 2025-06-18).

23 tools offered to AI assistants

  • 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 navig
  • 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-par
  • 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.
  • pause_session_task · Pause the task currently running in a browser session. Resume it later with resume_session_task.
  • resume_session_task · Resume a previously paused task in a browser session.
  • stop_session_task · Cancel the task currently running in a browser session, keeping the session alive for new tasks.
  • terminate_session · End a browser session and free its resources. The session and any running task cannot be resumed afterwards.
  • 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.
  • 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.
  • screenshot · Capture a screenshot of the current browser page in an active session. Returns the screenshot as an inline image. Read-only.
  • list_sessions · List all active browser sessions for this account. Read-only.
  • 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 aut
Show 11 more
  • 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
  • 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 lis
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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 contr
  • 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 en
  • pause_agent · Pause an active scheduled agent — it stops firing until resumed. Get agentId from list_agents.
  • 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).

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://api.webrun.ai/mcpDECLAREDSRC-001 Official MCP Registry10h ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry10h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry10h ago
Websitehttps://webrun.aiDECLAREDSRC-001 Official MCP Registry10h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry10h ago
Version1.0.2DECLAREDSRC-001 Official MCP Registry10h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry10h ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run WebRun Browser Automation? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor WebRun Browser AutomationLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of WebRun Browser Automation?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/webrun-browser-automation?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/webrun-browser-automation/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about WebRun Browser Automation

How do I connect WebRun Browser Automation?

Use the hosted endpoint https://api.webrun.ai/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

Does WebRun Browser Automation need an API key or token?

Yes. The registry entry lists a required value: Authorization. Get it from the publisher.

What tools does WebRun Browser Automation offer?

When Electra Index connected on 13 Nov 2026, it listed 23 tools: browser_task, create_session, send_task, pause_session_task, resume_session_task, stop_session_task, terminate_session, guardrail_response and more. The full list is in "Live check" above.

Is WebRun Browser Automation online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 2d ago.

What can I use WebRun Browser Automation for?

Based on its description, it is most relevant to: fill web forms automatically, test web applications, book appointments online, collect data behind logins.