Skip to main content

Documentation Index

Fetch the complete documentation index at: https://jam.dev/docs/llms.txt

Use this file to discover all available pages before exploring further.

AI agent debugging a Jam via MCP, with calls to getConsoleLogs, getNetworkErrors, and getUserEvents tools Jam MCP (Model Context Protocol) lets your AI coding tools open a Jam recording and automatically load its full context (video, user events, console logs, errors, and network requests) right where you’re working. Paste a Jam link into any supported MCP client and the context flows directly to your agent. Jam captures console logs, network requests, user events, and your chosen metadata automatically when you record. With MCP, that context flows into Claude Code, Cursor, VS Code, and Windsurf without copy-pasting.

Prerequisites

You need a Jam recording before your agent can use MCP.
1

Install the Jam Chrome extension

Install the Jam extension from the Chrome Web Store.
2

Record a Jam

Hit Record to capture your screen and voice.
3

Copy your Jam link

Stop the recording. Your Jam link is ready for an agent to consume via MCP.

Step 1: Configure your MCP client

1

Open settings

From the ChatGPT home page, go to Settings.
2

Navigate to connectors

Click Apps & Connectors.
3

Connect Jam

Select Jam and click the Connect button.
4

Authorize

Sign in to Jam and allow access to your workspace.

Step 2: Start using Jam MCP

Once your MCP client is configured:
1

Copy your Jam link

Copy one or more Jam links from your workspace.
2

Prompt your agent

Paste the Jam link into your agent’s chat and describe what you need. See the prompting tips and examples below.
3

Authenticate

Authenticate your IDE with Jam when prompted.
4

Approve tool requests

Approve any tool requests the agent makes as it reads your Jam data.

Available MCP tools

ToolDescription
getDetailsGet a quick snapshot of the Jam: who made it, what happened, and which other tools to try next.
getConsoleLogsGrab the console logs from the Jam. Supports logLevel and limit filters to reduce noise.
getNetworkRequestsList every web request from the Jam as JSON. Supports statusCode, contentType, host, and limit filters.
getScreenshotGet every screenshot from a screenshot Jam for visual inspection.
getUserEventsRead each click, input, and page navigation change in plain language.
getMetadataRead custom key-value metadata set via the jam.metadata() SDK: user IDs, app versions, feature flags, and more.
getVideoTranscriptGet the spoken transcript from a video Jam where the microphone was enabled, in WebVTT format with timestamps.
analyzeVideoAnalyze a Jam video recording to extract insights, detect issues, and provide structured feedback.
listJamsSearch and filter Jams by text, type, folder, author, URL, or date.
listMembersBrowse your team members.
listFoldersBrowse available folders.
createCommentAdd Markdown comments to a Jam.
updateJamMove Jams between folders using a folder ID or folder name.
getScreenshot and analyzeVideo are not available for Instant Replay Jams. All other MCP tools work and return data for Instant Replay Jams.

Prompting tips

  • Use Jam MCP to help with bug analysis, product feedback, and giving agents the context they need to debug issues.
  • Be as specific as you would with another engineer for the best results.
  • Start with small features or bug fixes. Tell your agent to propose a plan using Jam MCP and verify its plan before moving on to suggested edits.

Examples

Here are three ways the team at Jam uses Jam MCP in their own workflow.

Bug analysis

Tomasz (Product Engineer) uses Jam MCP to debug issues by providing bug context to Cursor to ship a fix.
Review this Jam [Jam Link] and analyze the problem, cross-reference it with the existing codebase, and prepare a detailed plan for implementation.
Stack: Jam recordings + Jam MCP + Cursor

Product feedback triage

Frits (Product Manager) lets Claude review and analyze customer Jams to spot common issues and patterns, then turns findings into grouped Linear tickets.
Analyze these Jams, perform root-cause analysis, and organize them into efficient work packages to minimize engineers' context switching; create Linear tickets from the analysis.

[Jam Link]
Stack: Jam customer recordings + Jam MCP + Claude Desktop + Linear MCP

Implementation planning from design feedback

Martin (Product Designer) records product and design feedback with the Jam extension. Jam MCP provides the context for Claude Code to plan and ship a ready-to-review PR.
I recorded product feedback in a Jam. Create an implementation plan for the changes requested in this Jam:

[Jam Link]
Stack: Jam extension + Jam MCP + Claude Code inside Cursor

Managing MCP access

Go to Settings → MCP to see connected tools. Select any tool to revoke or disconnect access at any time.
MCP mirrors your existing Jam permissions. It does not grant new access beyond what a user can already see in the Jam web or mobile apps. Use your normal admin controls for members and roles, or SSO in Settings.

FAQ

Yes. You only need an existing Jam link. Anyone (you, your workspace, or a customer) can record a Jam. If you want to record and create new Jams yourself, install the Chrome extension or use the iOS app.
Some MCP tools use Google’s Gemini. Jam opts out of training on customer data and takes steps to de-identify it. See the Security page for more details on Jam’s AI data policy.
Not exactly. getScreenshot and analyzeVideo are not available for Instant Replay Jams. All other MCP tools still work and return data and context.
MCP mirrors your existing Jam permissions. It doesn’t grant new access. Use your normal admin controls for members and roles, or SSO in Settings. Nothing is exposed via MCP that a user couldn’t already see in the Jam web or mobile apps.