Rrweb Stack vs Real Browser MCP

A side-by-side look at the Rrweb Stack and Real Browser MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Rrweb Stack logoRrweb StackBrowser Automation · Local subprocess (stdio)Local-first MCP server (@peekdev/mcp) + Chrome extension that records your real authenticated browser session (rrweb DOM + console + network, PII-masked, to local SQLite) and lets AI coding agents query it or drive the browser. No cloud, no telemetry.51GoodAuth: no auth requiredReal Browser MCP logoReal Browser MCPBrowser Automation · Local subprocess (stdio)MCP server + Chrome extension that gives AI agents control of the user's real browser with existing sessions, logins, and cookies. No headless browser, no re-authentication.68GreatAuth: no auth required

Verdict: choose Rrweb Stack for browser automation work as a local process; choose Real Browser MCP for browser automation as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Rrweb Stack logoChoose Rrweb Stack 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.
Explore Rrweb Stack

Real Browser MCP logoChoose Real Browser MCP 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_navigate, browser_click, browser_type.
Explore Real Browser MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecRrweb Stack logoRrweb StackReal Browser MCP logoReal Browser MCP
CategoryBrowser AutomationBrowser Automation
Quality signal51/100 · Good68/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNo auth required
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars857
Directory activity 4 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
ToolsNot listed18

Tools & capabilities

Rrweb Stack tools

No tool names declared yet. Check the project README from the listing page.

Real Browser MCP tools 18

  • browser_navigateNavigate to a URL in the active browser tab
  • browser_clickClick an element on the page using a ref from snapshot or a CSS selector
  • browser_typeType text into an input element
  • browser_scrollScroll the page or an element. Supports pixel offsets, scrolling to elements, and named positions (top/bottom). Works with virtual scroll containers used by social media sites.
  • browser_press_keyPress a keyboard key or combination (Enter, Escape, Tab, ArrowDown, etc). Supports modifiers like Ctrl+A, Cmd+C.
  • browser_waitWait for a condition: element to appear, element to disappear, or a fixed delay. Useful for SPAs and dynamic content.
  • browser_snapshotGet an accessibility tree snapshot of the page. Returns element refs you can use with click, type, and other tools. Use compact mode (default) for smaller output - only interactive elements.
  • browser_screenshotCapture a screenshot of the visible page area
  • browser_consoleRead console messages (log, warn, error) from the browser
  • browser_networkRead network requests made by the page. Filter by URL pattern.
  • browser_tabsManage browser tabs: list, create, close, or focus
  • browser_findFind elements on the page using natural language (e.g. "login button", "search input"). Returns refs you can use with click/type.
  • +6 more on 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.

Rrweb Stack

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "cubenest-rrweb-stack": {
      "command": "npx",
      "args": [
        "-y",
        "@tracelane/cli"
      ]
    }
  }
}

Real Browser MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "ofershap-real-browser-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "real-browser-mcp"
      ]
    }
  }
}

Frequently asked questions

Rrweb Stack is categorized under Browser Automation and uses a local stdio subprocess. Real Browser MCP belongs to Browser Automation and uses a local stdio subprocess. Pick Rrweb Stack for browser automation work and Real Browser MCP 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.

Rrweb Stack is listed as free. Auth: no auth required. Real Browser MCP is listed as free. Auth: no auth required. 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 cubenest-rrweb-stack and ofershap-real-browser-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Rrweb Stack has a quality signal of 51/100 (Good) with 4 views, 0 installs and 8 GitHub stars. Real Browser MCP has 68/100 (Great) with 6 views, 0 installs and 57 GitHub stars.