Productivity · Remote MCP server
WebRun Browser Automation
Run multi-step tasks in a real Chrome browser: persistent environments, live view, human takeover.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.webrun/webrun- Version
- 1.0.2
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP
- Published
- 2026-08-08
- Updated
- 2026-08-08
- Publisher
- ai.webrun
- Namespace
- Namespace verified by the MCP Registry via the domain webrun.ai · how
- Listed under
- Browser automation MCP servers
- Website
- webrun.ai
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.webrun.ai/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- webrun 2.0.0 · protocol 2025-06-18
- Tools discovered
21 - show names
browser_task,create_session,send_task,pause_session_task,resume_session_task,stop_session_task,terminate_session,guardrail_response,get_task_status,screenshot,list_sessions,list_environments,list_workflows,get_workflow,create_workflow,update_workflow,trigger_workflow,create_agent,list_agents,pause_agent,resume_agent- Checked on
- 2026-10-05
How to connect WebRun Browser Automation
WebRun Browser Automation is a remote MCP server: there is nothing to install. Its endpoint is https://api.webrun.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| wcagc - accessibility scanningDeterministic axe-core accessibility scans (WCAG 2.1 AA, EN 301 549, PDF/UA) via your account. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Web Remote JobsDiscover US remote roles, match your experience, and create tailored resumes and cover letters. | Remote · HTTPLive check: sign-in required |
| Web TaskBrowser tasks, sessions, and recipes for MCP and HTTP automation. | Local · stdio |
| webhook-inboxEphemeral HTTPS inbox for bots: mint URL, capture POSTs, list JSON. TEST. https://inbox.kymac.co. | Remote · HTTPLive check: ✗ no handshake |
| Website Email Extractor, Phone & Contact Finder (CSV, Sheet)Published emails, phones and social profiles for every website in a list, CSV or Google Sheet. | Remote · HTTPLive check: sign-in required |
| WebtzmManage Webtzm forms that send submissions to Google Sheets: list, embed, create, update, pause. | Remote · HTTPLive check: sign-in required |
| Webweaver MCP ServerWebWeaver Nexus services for MCP hosts: contact form (with UI), product overview, contact links. | Remote · HTTPLive check: ✓ handshake |
| Weekness - Week & Calendar UtilitiesMCP server with ISO week and calendar tools for date conversion, week math, and weekday lookups. | Local · stdio |