In-depth architectural comparison of the Rrweb Stack and Selenix MCP Server 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: 55/100 (Good) | Auth: No auth required
Selenix MCP Server
Browser Automation · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Verdict Summary: Choose Rrweb Stack if you need specialized Browser Automation tools running via a local process. Choose Selenix MCP Server if your workspace requires Browser Automation integration with local subprocess execution. 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).
You have access to required keys: PEEK_MCP_API_KEY, PEEK_MCP_PORT.
Primary tools included: Browser session recording with DOM, console, and network capture, Local SQLite storage with PII masking and large-DOM throttling, Permission-gated live browser control for AI agents.
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.
MCP server bridging Claude Desktop with Selenix for browser automation and testing. Create, run, debug, and manage browser tests through natural language.
Category & Scope
Tools & Capabilities Breakdown
Rrweb Stack Tools (6)
Browser session recording with DOM, console, and network capture
Local SQLite storage with PII masking and large-DOM throttling
Permission-gated live browser control for AI agents
Self-contained HTML reports for test session replay
Supports WebdriverIO and Playwright with Cypress planned
Open-source rrweb fork with compression and screenshot fallback
Selenix MCP Server Tools (18)
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, Selenix MCP Server belongs to Browser Automation using local stdio subprocess. Select Rrweb Stack when you need capabilities focused on browser automation and Selenix MCP Server when you require tools for browser automation.