Vibe MCP — Real Chrome, Remotely vs Pagerunner

In-depth architectural comparison of the Vibe MCP — Real Chrome, Remotely and Pagerunner MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Vibe MCP — Real Chrome, Remotely when:

• You need dedicated capabilities in the Browser Automation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: navigate_to_url, go_back, click.

Explore Vibe MCP — Real Chrome, Remotely Details

Choose Pagerunner when:

• You need dedicated capabilities in the Browser Automation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: list_profiles, open_session, attach_session.

Explore Pagerunner Details

Feature & Specification Comparison

Specification	Vibe MCP — Real Chrome, Remotely Browser Automation	Pagerunner Browser Automation
Summary	Drive your real, logged-in Chrome from any MCP client — even from a remote machine, no inbound port.	Chrome browser automation MCP server for AI agents — drives real Chrome with your profiles
Category & Scope	Browser Automation	Browser Automation

Tools & Capabilities Breakdown

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).

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

{
  "mcpServers": {
    "pagerunner": {
      "command": "npx",
      "args": [
        "-y",
        "pagerunner"
      ]
    }
  }
}

Related MCP Server Comparisons