Jam

Record screen and collect automatic context for issues

Jam's MCP is the fast lane between Jam recordings and your dev tools. Drop a Jam link into VS Code, Cursor, Windsurf, or Claude and the whole recording – video, console, network, logs – arrives pre-packaged. No hand-typing repro steps, no copy-paste stack traces, no screen-share drama. Your tools get instant context, you stay in flow.

Install

1Add the server to Claude Code

claude mcp add --transport http jam https://mcp.jam.dev/mcp

2Sign in

Run /mcp in Claude Code and complete the login flow for this server.

These instructions target Claude Code. Check the publisher's documentation for support in other Claude surfaces; a valid server URL alone does not establish compatibility.

JSON.mcp.json for a shared project

Commit this file so everyone on the project gets the same server.

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

Tools

  • getDetails
  • getConsoleLogs
  • getNetworkRequests
  • getScreenshot
  • getUserEvents
  • analyzeVideo

About

The fast lane between Jam recordings and your dev tools. Drop a Jam link into Claude and the whole recording – video, console, network, logs – arrives pre-packaged. No hand-typing repro steps, no copy-paste stack traces, no screen-share drama. Claude gets instant context, you stay in flow.

You can use the Jam connector to:

Analyze bugs and create implementation plans:
"Review this Jam <Jam Link> and analyze the problem, cross-reference it with the existing codebase, and prepare a detailed plan for implementation"

Perform root-cause analysis and organize work:
"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>"

Turn product feedback into action plans:
"I recorded product feedback in a Jam. Create an implementation plan for the changes requested in this Jam: <Jam Link>"

Discussion

Discussion

0