MCP Server Browser vs WebRun Browser Automation
A side-by-side look at the MCP Server Browser and WebRun Browser Automation MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
W
WebRun Browser AutomationBrowser AutomationRun multi-step tasks in a real Chrome browser: persistent environments, live view, human takeover.37FairAuth: not declaredVerdict: choose MCP Server Browser for browser automation work as a local process; choose WebRun Browser Automation for browser automation. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Server Browser when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
browser_click, browser_close, browser_close_tab.
WChoose WebRun Browser Automation when
- You need dedicated capabilities in the Browser Automation domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | W WebRun Browser Automation | |
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 67/100 · Great | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 39,368 | — |
| Directory activity | 6 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 23 | Not listed |
| Full listing | View MCP Server Browser | View WebRun Browser Automation |
Tools & capabilities
MCP Server Browser tools 23
browser_clickClick an element on the page, before using the tool, use `browser_get_clickable_elements` to get the index of the element, but not call `browser_get_clickable_elements` multiple timesbrowser_closeClose the browser when the task is done and the browser is not needed anymorebrowser_close_tabClose the current tabbrowser_evaluateExecute JavaScript in the browser consolebrowser_form_input_fillFill out an input field, before using the tool, Either 'index' or 'selector' must be providedbrowser_get_clickable_elementsGet the clickable or hoverable or selectable elements on the current page, don't call this tool multiple timesbrowser_get_download_listGet the list of downloaded filesbrowser_get_markdownGet the markdown content of the current pagebrowser_get_textGet the text content of the current pagebrowser_go_backGo back to the previous pagebrowser_go_forwardGo forward to the next pagebrowser_hoverHover an element on the page, Either 'index' or 'selector' must be provided- +11 more on the listing page
WebRun Browser Automation tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Server Browser
{
"mcpServers": {
"agent-infra-mcp-server-browser": {
"command": "npx",
"args": [
"-y",
"@agent-infra/mcp-server-browser"
]
}
}
}
WebRun Browser Automation
No confirmed install command for WebRun Browser Automation yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
MCP Server Browser is categorized under Browser Automation and uses a local stdio subprocess. WebRun Browser Automation belongs to Browser Automation and uses an install path we have not confirmed yet. Pick MCP Server Browser for browser automation work and WebRun Browser Automation for browser automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. WebRun Browser Automation has no confirmed install command yet — follow its own setup instructions.
MCP Server Browser is listed as free. Auth: no auth required. WebRun Browser Automation has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add agent-infra-mcp-server-browser and webrun-browser-automation as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Server Browser has a quality signal of 67/100 (Great) with 6 views, 0 installs and 39,368 GitHub stars. WebRun Browser Automation has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
