Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest
关于 Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
Two OSS products on one rrweb substrate: tracelane (self-contained HTML test-failure replays for WDIO/Playwright/Cypress) + peek (local-first browser-session forensics + repro for AI coding agents, over MCP). No SaaS, no telemetry, local-first.
基本信息
配置
使用下面的配置,将此服务器添加到你的 MCP 客户端。
{
"mcpServers": {
"peek": {
"command": "npx",
"args": [
"-y",
"@peekdev/mcp"
]
}
}
}工具
未检测到工具
工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。
概览
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.
开发工具 分类下的更多 MCP 服务器
Deepwiki MCP Server
regenrek📖 MCP server for fetch deepwiki.com and get latest knowledge in Cursor and other Code Editors
MCP-Bridge
SecretiveShellA middleware to provide an openAI compatible endpoint that can call MCP tools
MCP Unity Editor (Game Engine)
CoderGamesterModel Context Protocol (MCP) plugin to connect with Unity Editor — designed for Cursor, Claude Code, Codex, Windsurf and other IDEs
nuxt-mcp / vite-plugin-mcp
antfuMCP server helping models to understand your Vite/Nuxt app better.
Golf
golf-mcpProduction-Ready MCP Server Framework • Build, deploy & scale secure AI agent infrastructure • Includes Auth, Observability, Debugger, Telemetry & Runtime • Run real-world MCPs powering AI Agents
评论