HelpLoginSign up for free

MCP

Overview

Jam MCP (Model Context Protocol) lets your developer tools and AI agents open a Jam recording and automatically load its data into context (video, user events, console logs, errors and network requests). As a developer, you’ll debug faster without hand-typing steps to reproduce, copy-pasting stack traces, or screen-sharing.

Your AI models and agents can use Jam’s MCP server to access your Jam recordings and their data in a simple and secure way.

Paste an existing Jam link into supported MCP clients like VS Code, Cursor, Windsurf, or Claude Code, and the Jam's context appears right where you’re working.

Prerequisites

Record a Jam first

  1. Install the Jam Chrome extension.

  2. Hit Record to capture your screen and voice.

  3. Stop the recording, and your Jam link is ready for an agent to consume via MCP.

1. Configure

Claude Desktop

Steps:

  1. From the home page click search and tools on web or desktop

  2. Click +Add connectors

  3. Find Jam in the Connector Directory and click the button to connect

  4. Sign in to Jam and pick the workspace Claude should access

Claude Code

Steps:

  1. Install Claude Code in your IDE

  2. In your terminal run

claude mcp add Jam https://mcp.jam.dev/mcp -t http -s user
Cursor

Add to cursor

{
  "mcpServers": {
    "jam": {
      "url": "https://mcp.jam.dev/mcp"
    }
  }
}

Once you make the above changes, make sure to restart Cursor to use Jam.

Visual Studio Code

  1. CTRL/CMDP + P and enter >MCP: Add Server

  2. Select HTTP (HTTP or Server-Sent Events)

  3. Enter https://mcp.jam.dev/mcp

  4. Enter Jam

  5. Your mcp.json file should look like this: 

{
  "servers": {
    "Jam": {
      "url": "https://mcp.jam.dev/mcp",
      "type": "http"
      
    }
  }
}
Windsurf

  1. CTRL/CMDP + P and enter >MCP: Add Server

  2. Select HTTP (Server-Sent Events)

  3. Enter https://mcp.jam.dev/mcp

  4. Enter Jam

  5. Your mcp.json file should look like this: 

{
    "mcp": {
        "servers": {
            "Jam": {
                "type": "http",
                "url": "https://mcp.jam.dev/mcp"
            }
        }
    }
}

Jam MCP is backwards compatible with the deprecated HTTP+SSE transport

2. Getting Started

Once you have configured your MCP:

  1. Copy one or multiple Jam links

  2. Prompt your agent and paste the Jam link. See our prompt tips and examples below

  3. Authenticate your IDE with Jam

  4. Approve any of the tool requests the agent makes

3. Available Features in Jam MCP

Tools

Tool name
Description

getDetails

Get a quick snapshot of the Jam. Who made it, what happened, and which other tools to try next.

getConsoleLogs

Grab the console logs from the Jam

getNetworkRequests

List every web request from the Jam as JSON, trimmed to the essentials for fast debugging.

getScreenshot

Get every screenshot from a screenshot Jam so you can inspect

getUserEvents

Read each click, input and page navigation change in plain language.

analyzeVideo

Analyzes Jam video recordings to extract insights, detect issues, and provide structured feedback.

4. Tips

Prompting tips:

  1. Use Jam MCP to help with bug analysis, product feedback, and give agents context to debug issues.

  2. Be as specific as you would with another engineer for the best results

  3. 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

5. Examples

Examples of how the team at Jam uses Jam MCP:

Tomasz (Product Engineer) Uses Jam MCP to debug issues, by providing the context of a bug to Cursor, to ship a fix.

Prompt
Review this Jam <Jam Link Placeholder> and analyze the problem, cross-reference it with the existing codebase, and prepare a detailed plan for implementation.
Stack used

Frits (Product Manager) let’s Claude review and analyze customer Jams to spot common issues and patterns. Claude turns the findings into neatly grouped Linear tickets.

Prompt
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 Placeholder>
Stack used

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 with the implemented Feedback.

Prompt
I recorded product feedback in a Jam. Create an implementation plan for the changes requested in this Jam:

<Jam Link Placeholder>
Stack used

6. Feedback

Got an idea that would make Jam MCP faster, smarter or more useful? Drop it in the form below (30 seconds, tops).

Request a feature

FAQ

Can I use MCP without the Chrome extension?

Yes. You only need an existing Jam link. Anyone (you, your team, or a customer) can record a Jam. If you want to record and create new Jams, install the Chrome extension or use our iOS app.

Can I paste multiple Jam links at once?

Yes. You can paste more than one link, but we recommend one Jam at a time so your agent doesn’t hit context window limits.

How do I review or revoke tools that can access Jam via MCP?

Go to Settings → Integrations → AI Agents to see connected tools. Select a tool to revoke or disconnect access at any time.

Does Jam MCP send my Jam data to third parties?

Some MCP tools use Google’s Gemini. We opt out of training on Jam customer data and take steps to de-identify it. See our AI Policies for more details.

Does MCP work the same with Instant Replay Jams?

Not exactly. getScreenshot and videoAnalysis are not available for Instant Replay Jams. Other MCP tools still work and return data/context.

How can admins control what MCP can access?

MCP mirrors your existing Jam permissions. It doesn’t grant new access. Use your normal admin controls for members and roles, or SSO in workspace settings. Nothing is exposed via MCP that a user couldn’t already see in the Jam web or mobile apps.

PreviousJam.MetadataNextAsana

Last updated

Was this helpful?