Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.

What is peek?

peek is a local-first MCP server that brings your real authenticated browser session to AI coding agents. It pairs a Chrome MV3 extension with a stdio MCP server to record and expose browser sessions, and—with explicit per-origin consent—allows the agent to read and drive the live page. No cloud, no telemetry; everything stays on your machine.

How to use peek?

Install the CLI globally (npm install -g @peekdev/cli), then run npx peek init. The Chrome MV3 extension is installed from the Chrome Web Store. Once running, use peek sessions list and peek sessions show --format markdown to query recorded sessions. The MCP server (@peekdev/mcp) runs over stdio and exposes captured sessions plus consent-gated live read/act tools to MCP clients such as Claude Code, Cursor, Cline, and Windsurf.

Key features of peek

• Local-first: no cloud, no telemetry, all data in ~/.peek
• Chrome MV3 extension records real browser sessions
• MCP server exposes sessions as structured, AI‑ready data
• Consent‑gated live read and act tools for AI agents
• Five‑level per‑origin permission model (default: Read‑only)
• Destructive‑action blocklist always prompts for confirmation

Use cases of peek

• AI coding agents inspect recorded browser sessions to debug user workflows
• Developers grant an agent read‑only access to a live page for suggestions
• Agents fill forms or click UI elements with explicit user confirmation
• QA engineers share session snapshots locally without uploading to a SaaS
• Security audits of web app interactions without third‑party services

FAQ from peek

What runtime does peek require?

Node.js 22 or later. The better-sqlite3 dependency ships prebuilt binaries only for Node 22+; older Node versions fall back to native compilation and may fail.

Where does recorded session data live?

All session data stays in ~/.peek on your local machine. No data is sent to any cloud service.

How does the permission model work for live actions?

A five‑level per‑origin model: 0 Off, 1 Read‑only (default), 2 Suggest‑only, 3 Act‑with‑confirm, 4 YOLO. Destructive actions always prompt for confirmation regardless of level.

Does peek collect telemetry?

No telemetry is collected. The extension and server are fully local.

Which AI coding tools does peek support?

The MCP server works with any MCP‑compatible client, including Claude Code, Cursor, Cline, and Windsurf.