Code

Jam

by Jam

Overview

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.

Tools

Jam tools

ChatGPT

Screen record with context

analyzeVideo

ChatGPT

Extract user intents from a Jam recording. Identifies distinct user goals, issues, and feedback with detailed context including visual observations, interactions, and technical indicators.

fetch

ChatGPT

Retrieve comprehensive metadata and details for a specific Jam bug report. Returns essential information including: unique identifiers, author details, description, timestamps (created/updated), type (video/screenshot), and associated metadata. This is the primary entry point for analyzing any Jam - always call this tool first to understand the context before using other tools.

getConsoleLogs

ChatGPT

Retrieve all browser console output captured during the Jam session. Includes JavaScript errors, warnings, info messages, debug logs, and stack traces. Critical for identifying runtime errors, debugging application state issues, and understanding the sequence of events leading to bugs.

getDetails

ChatGPT

getNetworkRequests

ChatGPT

Extract complete network activity logs captured during the Jam session. Returns all HTTP/HTTPS requests including: URLs, methods (GET/POST/etc), status codes, headers, payloads, response times, and error details. Essential for debugging API issues, failed requests, CORS problems, and performance bottlenecks.

getScreenshots

ChatGPT

Retrieve visual screenshots and image attachments from screenshot-type Jams. Returns image data that can be analyzed for UI issues, visual bugs, layout problems, or design inconsistencies. Note: This tool only works with Jams of type 'screenshot' - use getDetails first to verify Jam type.

getUserEvents

ChatGPT

Access the complete timeline of user interactions captured in the Jam. Returns chronological sequence of: clicks, keyboard inputs, form submissions, navigation events, scroll actions, and other DOM interactions. Invaluable for reproducing bugs and understanding user behavior patterns that triggered issues.