What is the key difference between Vibe MCP — Real Chrome, Remotely and WebRun Browser Automation?

Vibe MCP — Real Chrome, Remotely belongs to the Browser Automation category with local stdio execution, while WebRun Browser Automation belongs to the Browser Automation category with local stdio execution.

How do I install Vibe MCP — Real Chrome, Remotely or WebRun Browser Automation in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Vibe MCP — Real Chrome, Remotely and WebRun Browser Automation free or paid?

Vibe MCP — Real Chrome, Remotely operates under a Free / Open Source model (No auth required). WebRun Browser Automation operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Vibe MCP — Real Chrome, Remotely lists 10 tools with 0 views and 3 GitHub stars. WebRun Browser Automation lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Vibe MCP — Real Chrome, Remotely and WebRun Browser Automation together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Vibe MCP — Real Chrom… vs WebRun Browser Automa…

Vibe MCP — Real Chrom… vs WebRun Browser Automa… | AllMCPs

Feature & Specification Comparison

Specification	Vibe MCP — Real Chrome, Remotely Browser Automation	W WebRun Browser Automation Browser Automation
Summary	Drive your real, logged-in Chrome from any MCP client — even from a remote machine, no inbound port.	Run multi-step tasks in a real Chrome browser: persistent environments, live view, human takeover.
Category & Scope	Browser Automation	Browser Automation
Quality signal	56/100 (Good)	37/100 (Fair)
Transport Protocol	Local Subprocess (stdio)	Local Subprocess (stdio)
Auth Requirement	No auth required	No auth required
Pricing Model	Free / Open Source	Free / Open Source
Required Env Vars	None required	None required
Compatible Clients	Claude DesktopCursorWindsurfClineVS Code	Claude DesktopCursorWindsurfClineVS Code
Install path signal	`npx · high`	`npx · low`
Engagement & Health	0 views 0 copies 0 upvotes 3 stars	0 views 0 copies 0 upvotes
Verified / Official	Community Listing	Community Listing
Open full listing	View Vibe MCP — Real Chrome, Remotely Listing	View WebRun Browser Automation Listing

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Vibe MCP — Real Chrome, Remotely Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "vibe-mcp-real-chrome-remotely": {
      "command": "npx",
      "args": [
        "-y",
        "@vibebrowser/cli@latest"
      ]
    }
  }
}

WebRun Browser Automation Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "webrun-browser-automation": {
      "command": "npx",
      "args": [
        "-y",
        "webrun-browser-automation"
      ]
    }
  }
}

Vibe MCP — Real Chrome, Remotely vs WebRun Browser Automation

At a Glance & Executive Verdict

Which MCP Server Should You Choose?

Choose Vibe MCP — Real Chrome, Remotely when:

Choose WebRun Browser Automation when:

Feature & Specification Comparison

Tools & Capabilities Breakdown

Vibe MCP — Real Chrome, Remotely Tools (10)

WebRun Browser Automation Tools (0)

Ready-to-Paste Client Configurations

Frequently Asked Questions

Related MCP Server Comparisons

Popular comparisons with Vibe MCP — Real Chrome, Remotely

Popular comparisons with WebRun Browser Automation