Getting started

Run the MCP server, point your AI client at it, load the extension.

1. Run the MCP server

The simplest path is npx — no install needed. Your AI client will spawn the server for you on demand:

npx -y @peekdev/mcp

This runs the stdio MCP server (it reads and writes the local SQLite at ~/.peek/sessions.db). You generally won't invoke it directly — your AI client (next step) does that.

2. Configure your AI client

Add peek as an MCP server in your client's config. Pick the one you use:

Claude Code — `~/.claude.json`

{
  "mcpServers": {
    "peek": {
      "command": "npx",
      "args": ["-y", "@peekdev/mcp"]
    }
  }
}

Cursor — `~/.cursor/mcp.json`

{
  "mcpServers": {
    "peek": {
      "command": "npx",
      "args": ["-y", "@peekdev/mcp"]
    }
  }
}

VS Code Copilot — `.vscode/mcp.json`

{
  "servers": {
    "peek": {
      "command": "npx",
      "args": ["-y", "@peekdev/mcp"]
    }
  }
}

Or let the CLI do it all. Install @peekdev/cli and run peek init — it detects installed AI clients, writes the right MCP config for each, and registers the native messaging host with your browsers (macOS: ~/Library/Application Support/Google/Chrome/NativeMessagingHosts/; Linux: ~/.config/google-chrome/NativeMessagingHosts/; Windows: a registry key under HKCU\\Software\\Google\\Chrome\\NativeMessagingHosts). Consent-prompted; you choose which browsers to register.

npm install -g @peekdev/cli
peek init

3. Load the Chrome extension (alpha)

Until the Chrome Web Store listing is live (Phase 5), load the extension unpacked from a local build:

git clone https://github.com/Cubenest/rrweb-stack.git
cd rrweb-stack
pnpm install
pnpm build
pnpm --filter @peekdev/extension build

Open chrome://extensions.
Enable Developer mode (top right).
Click Load unpacked.
Select packages/peek-extension/.output/chrome-mv3/.

4. Enable peek on a site

Open the side panel from the toolbar.
Click Enable on this site. peek requests per-origin host permission from your user gesture and starts recording.
(Optional) Toggle Deep capture to record response bodies via chrome.debugger. Off by default.
(Optional) Set the per-origin permission level in the side panel. Default is Level 1 (observe-only).

5. Ask your agent

With the MCP server connected, ask your AI client things like:

“What did I just do on this page?” (replays the latest rrweb frames)
“Show me the failed network requests from the last 5 minutes.”
“What errors are in the console for example.com?”

Next steps

Privacy policy — what peek records and where it lives.
@peekdev/mcp README — full MCP tool surface.
@peekdev/cli README — peek init, sessions, audit log.
@peekdev/extension README — side-panel UI and per-site activation.
Manual QA checklist — end-to-end walk of the install path the maintainer used to verify this alpha.

Stuck? Open an issue on GitHub.