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.

MCP Server Browser logoMCP Server BrowserBrowser Automation · Local subprocess (stdio)The Open-Source Multimodal AI Agent Stack: Connecting Cutting-Edge AI Models and Agent Infra52GoodAuth: not declared
W
WebRun Browser AutomationBrowser Automation
Run multi-step tasks in a real Chrome browser: persistent environments, live view, human takeover.37FairAuth: not declared

Verdict: 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?

MCP Server Browser logoChoose MCP Server Browser when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
Explore MCP Server Browser

W
Choose WebRun Browser Automation when

  • You need dedicated capabilities in the Browser Automation domain.
Explore WebRun Browser Automation

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCP Server Browser logoMCP Server Browser
W
WebRun Browser Automation
CategoryBrowser AutomationBrowser Automation
Quality signal52/100 · Good37/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars39,367—
Directory activity 2 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

MCP Server Browser tools

No tool names declared yet. Check the project README from 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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-server-browser": {
      "command": "npx",
      "args": [
        "-y",
        "@agent-tars/cli@latest"
      ]
    }
  }
}

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 has no declared pricing — check the project's own site. 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 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 52/100 (Good) with 2 views, 0 installs and 39,367 GitHub stars. WebRun Browser Automation has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.