Перейти к содержимому
Логотип WebRun

MCP-сервер WebRun

Какие серверы из официального реестра MCP принадлежат WebRun, отвечают ли они и что умеют. Всё это проверила программа, а не переписал человек со страницы продукта.

прочитано 2026-10-13

← Назад к WebRun

Чей это сервер
  • Имя в реестреai.webrun/webrunподтверждён в реестре MCP

Имя в реестре лежит в пространстве webrun.ai. Реестр пускает в такое пространство только того, кто доказал владение доменом через DNS или HTTP.

Что он ответилпроверено 2026-10-13
  • Состояниеотвечаетпроверено 2026-10-13
  • Инструменты21
  • Сервер называет себяwebrun
  • Версия сервера2.0.0
  • Версия протокола2025-06-18

2026-10-13 сервер ответил на initialize и tools/list без входа. Первый ответ за 355 мс.

Инструменты сервераинструментов: 21 · прочитано 2026-10-13
  • 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…

  • 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…

  • 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…

  • 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"…

  • 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, and any pending logins. Identify by workflowId…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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).

Как подключить

Добавьте сервер в конфиг MCP-клиента. Claude Desktop, Cursor и большинство других клиентов понимают такой вид:

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

Каждую строку нашла программа: запись в реестре, ответ самого сервера, спецификация, которая разбирается. Если строки нет, значит, мы этого не нашли, а не что этого нет.