A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
8 ★ · Cubenest/rrweb-stack · read from the repository page · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 8 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository Cubenest/rrweb-stack;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
rrweb-stack Two OSS products on one rrweb-based substrate. Both ship as npm packages today. | Product | One line | Install | |---|---|---| | **tracelane** | The recorder for your WebdriverIO and Playwright tests — Cypress on the roadmap. Self-contained HTML for every run — replay failures, audit successes, attach to any bug tracker. No SaaS, no dashboard, no signup. | npx @tracelane/cli init | | **peek** | Your real browser, exposed to your AI coding agent over MCP — the agent reads recorded sessions and, with your explicit consent, drives the live page. Never leaves your machine. | npm install -g @peekdev/cli && npx peek init | *Above: npx @tracelane/cli init in a real WebdriverIO project — detect runner, install, edit wdio.conf.ts, ignore reports dir.* *Above: peek sessions list then peek sessions show ... --format markdown — a recorded browser session as queryable structured output, AI-ready.* What's where tracelane | Package | Status | What it does | |---|---|---| | @tracelane/wdio | alpha | WebdriverIO Service — capture + write HTML report | | @tracelane/playwright | alpha | Playwright Reporter + auto-fixture — capture + write HTML report | | @tracelane/cypress | planned | JSON-output adapter (no Test Replay overlap) | | @tracelane/core | alpha | Framework-agnostic capture engine — depended on by the adapters | | @tracelane/report | alpha | Self-contained HTML report builder | Docs: tracelane.cubenest.in (source under apps/tracelane-docs/). The tracelane-wdio README is the right starting point. peek | Package | Status | What it does | |---|---|---| | @peekdev/cli | alpha | peek init installer + peek sessions query / export | | @peekdev/mcp | alpha | stdio MCP server — exposes captured sessions, plus consent-gated live read + act tools, to Claude Code, Cursor, Cline, Windsurf | | peek-extension | alpha · on the Chrome Web Store | Chrome MV3 extension — the real browser, recorded | Docs: peek.cubenest.in (source under apps/peek-docs/). > **peek requires Node.js ≥ 22.** Its native better-sqlite3 dependency only > ships prebuilt binaries for Node 22+; on older Node (notably Windows, which > has no C/C++ toolchain by default) the install falls back to compiling from > source and fails. Shared substrate @cubenest/rrweb-core — vendored PostHog rrweb fork, PII masking primitives, large-DOM throttling, screenshot fallback, network/console capture abstractions, compression helpers. Used by both products. The fork is pinned by SHA + the substrate's NOTICE attributes both PostHog's plugin lineage and the upstream rrweb roots. Why two products, one repo Same recording engine, same trust model, two different consumer surfaces: - **tracelane** ships test-time captures into a self-contained HTML artifact your team and AI agents can read offline. - **peek** ships live-browser captures into an MCP server your AI coding agent can query — and, with your explicit per-origin consent, drive the live page through.