WebRun Browser Automation
Run multi-step tasks in a real Chrome browser: persistent environments, live view, human takeover.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http webrun-browser-automation 'https://api.webrun.ai/mcp' --header 'Authorization: <WebRun API key as a bearer token.>'
{
"mcpServers": {
"webrun-browser-automation": {
"type": "http",
"url": "https://api.webrun.ai/mcp",
"headers": {
"Authorization": "<WebRun API key as a bearer token.>"
}
}
}
}
Frequently asked questions
What is WebRun Browser Automation?
Run multi-step tasks in a real Chrome browser: persistent environments, live view, human takeover.
How do I install WebRun Browser Automation?
It runs as a remote server. In Claude Code: claude mcp add --transport http webrun-browser-automation 'https://api.webrun.ai/mcp' --header 'Authorization: <WebRun API key as a bearer token.>'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does WebRun Browser Automation need an API key?
Yes. It expects Authorization, which you set in its configuration.
Who maintains WebRun Browser Automation?
It is published by ai.webrun. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.