Set up peek with VS Code (Copilot) in 2 minutes

What you’ll end up with

peek’s MCP server registered with VS Code’s Copilot agent, verified by asking Copilot to call list_recent_sessions and seeing your recorded sessions.

Prerequisites

• VS Code with GitHub Copilot (agent mode / MCP support).
• Chrome with the peek extension installed — from the Chrome Web Store.
• At least one recorded session (browse with the extension on).

Steps

1. Add the MCP server to your workspace

Create .vscode/mcp.json in your project. VS Code uses the servers key — note this differs from the mcpServers key other clients use:

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

Or run peek init and choose VS Code — it writes the same .vscode/mcp.json for you.

2. Start the server and verify

Open the Copilot agent view, confirm peek is listed under MCP servers (start it if prompted), then ask:

List my recent peek sessions.

Copilot calls list_recent_sessions and shows your captured sessions.

Why this works

VS Code reads workspace MCP servers from .vscode/mcp.json under the servers key; type defaults to stdio when you provide command/args, so peek’s npx -y @peekdev/mcp@latest launches as a local stdio server.

Next steps

New to peek’s tools? See Using peek with your AI coding agent.

Trust & data handling

Read-tier by default: peek inspects sessions recorded locally in ~/.peek, non-mutating. Local-first: peek uploads nothing — what your MCP client does with the data is up to you. Captured values are masked at record time.