Index / MCP servers / WebRun Browser Automation

WebRun Browser Automation MCP server

Connect WebRun Browser Automation and your agent gets 21 tools, among them browser_task, create_agent, create_session. It answers at https://api.webrun.ai/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.

Status
Answering
Tools
21
Official
yes, served from webrun.ai
Reliability
10 of 10 checks
Response time
462 ms
Transport
streamable HTTP
Last checked
17 October 2026

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

Description as the publisher wrote it.

The 21 tools WebRun Browser Automation offers

ToolWhat it does
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 navig
Inputs: prompt, startingUrl, maxDuration, outputType, outputSchema, webhook
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 contr
Inputs: workflowId, schedule, expiresAt, name, variables, prompt
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-par
Inputs: mode, task, environmentId, policyId, debugC, proxy
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
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.
Inputs: sessionId, taskId
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
Inputs: workflowId, title
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.
Inputs: sessionId, response, newState, files
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 en
Inputs: scope
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 aut
list_sessionsList all active browser sessions for this account. Read-only.
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
Inputs: scope
pause_agentPause an active scheduled agent — it stops firing until resumed. Get agentId from list_agents.
Inputs: agentId
pause_session_taskPause the task currently running in a browser session. Resume it later with resume_session_task.
Inputs: sessionId
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).
Inputs: agentId
resume_session_taskResume a previously paused task in a browser session.
Inputs: sessionId
screenshotCapture a screenshot of the current browser page in an active session. Returns the screenshot as an inline image. Read-only.
Inputs: sessionId
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.
Inputs: sessionId, prompt, startingUrl, maxDuration, maxInputTokens, maxOutputTokens
stop_session_taskCancel the task currently running in a browser session, keeping the session alive for new tasks.
Inputs: sessionId
terminate_sessionEnd a browser session and free its resources. The session and any running task cannot be resumed afterwards.
Inputs: sessionId
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
Inputs: workflowId, title, variables, force
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

Add WebRun Browser Automation to your AI client

Every block below points at https://api.webrun.ai/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http webrun-browser-automation https://api.webrun.ai/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "webrun-browser-automation": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.webrun.ai/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "webrun-browser-automation": {
      "url": "https://api.webrun.ai/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "webrun-browser-automation": {
      "type": "http",
      "url": "https://api.webrun.ai/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "webrun-browser-automation": {
      "url": "https://api.webrun.ai/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "webrun-browser-automation": {
      "serverUrl": "https://api.webrun.ai/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "webrun-browser-automation": {
      "url": "https://api.webrun.ai/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: WebRun Browser Automation
version: 0.0.1
schema: v1
mcpServers:
  - name: WebRun Browser Automation
    type: streamable-http
    url: https://api.webrun.ai/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "webrun-browser-automation": {
      "httpUrl": "https://api.webrun.ai/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "webrun-browser-automation": {
      "type": "http",
      "url": "https://api.webrun.ai/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "webrun-browser-automation": {
      "url": "https://api.webrun.ai/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fapi.webrun.ai%2Fmcp&type=streamable_http&id=webrun-browser-automation&name=WebRun%20Browser%20Automation

Is WebRun Browser Automation up right now?

It answered our last check on 17 October 2026 in 462 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to WebRun Browser Automation

Questions about WebRun Browser Automation

Is there an official WebRun Browser Automation MCP server?

Yes. It is published by webrun.ai and served from api.webrun.ai, the vendor's own domain: https://api.webrun.ai/mcp.

How many tools does WebRun Browser Automation have?

21, as returned by the server's own tools/list on 9 September 2026: browser_task, create_agent, create_session, create_workflow, get_task_status, get_workflow, guardrail_response, list_agents, and 13 more.

Is WebRun Browser Automation down?

It answered our last check on 17 October 2026 in 462 ms. Over 10 checks since 4 September 2026 it answered 10.

How do I add WebRun Browser Automation to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.webrun.ai/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does WebRun Browser Automation need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: ai.webrun. Endpoint host: api.webrun.ai. ARD identifier: urn:air:ai.webrun:mcp:webrun. First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.