Rrweb Stack vs WebReaper — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Rrweb Stack vs WebReaper
In-depth architectural comparison of the Rrweb Stack and WebReaper 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.
At a Glance & Executive Verdict
Rrweb Stack
Browser Automation · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
WebReaper
Browser Automation · Remote HTTP/SSE
Quality: 53/100 (Good) | Auth: API Key required
Verdict Summary: Choose Rrweb Stack if you need specialized Browser Automation tools running via a local process. Choose WebReaper if your workspace requires Browser Automation integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Rrweb Stack 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: Local SQLite session storage, rrweb DOM and browser activity recording, Console and network capture.
You need dedicated capabilities in the Browser Automation domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: WEBREAPER_MCP_TOKEN.
Primary tools included: MCP tools for scraping, mapping, extraction, and crawling, Stdio and Streamable HTTP server variants, Markdown output by default.
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.
⃣ 🏠 🍎 🪟 🐧 - AI-native web scraper MCP server. Single binary, returns clean markdown, MIT-licensed Firecrawl alternative.
Category & Scope
Tools & Capabilities Breakdown
Rrweb Stack Tools (6)
Local SQLite session storage
rrweb DOM and browser activity recording
Console and network capture
PII masking
Consent-gated live browser read and act tools
Per-origin permission levels
WebReaper Tools (6)
MCP tools for scraping, mapping, extraction, and crawling
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).
Rrweb Stack is categorized under Browser Automation and uses a local stdio subprocess. In contrast, WebReaper belongs to Browser Automation using remote streaming HTTP/SSE transport. Select Rrweb Stack when you need capabilities focused on browser automation and WebReaper when you require tools for browser automation.