WebRun Browser Automation
ai.webrun/webrun
Run multi-step tasks in a real Chrome browser: persistent environments, live view, human takeover.
Description as published in the official MCP registry.
Answers, but requires sign-in before the handshake. Checked 2026-10-04.
What we measured
| Endpoint | https://api.webrun.ai/mcp | registry |
|---|---|---|
| Handshake | Answers, but requires sign-in before the handshake (594 ms) | our check, 2026-10-04 |
| Registry version | 1.0.2 · active · updated 2026-08-08 | registry |
Signed reports
No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows a real call went through, not just an opinion. How to file one.
Connect
claude mcp add --transport http webrun https://api.webrun.ai/mcpCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Related servers
- Oya Browser Real Chrome for agents: start a browser, read pages as numbered markdown, click, type…
- Browser Automation Agent by Nova (CIVAI) I do everything related to Browser Automation & Management
- browser-automation Programmatic headless browser sessions: create, interact, browse, and extract - rendered…
- browser-use Control a real Chrome browser to complete any task: fill forms, extract data, book…
- walkerOS Source Browser Generate, parse, and validate walkerOS data-elb HTML tagging attributes
- Browser Automation Browser automation MCP server: navigate, fill forms, click, screenshot, and manage tabs
Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name ai.webrun/webrun.