Jam

Capture and report bugs with automatic screen recordings and environment details.

CommunityOnlineNo sign-inGlobalFreeCan modify data

What it can do

GetDetails: Retrieve comprehensive metadata and details for a specific Jam bug report. Returns essential information including: unique identifiers, author details, description, timestamps (created/upd
GetNetworkRequests: Extract network activity logs captured during the Jam session. Returns HTTP/HTTPS requests including: URLs, methods (GET/POST/etc), status codes, headers, payloads, response times,
GetConsoleLogs: Retrieve browser console output captured during the Jam session. Includes JavaScript errors, warnings, info messages, debug logs, and stack traces. Use logLevel filter to focus on spec

What data it sees

Do you need an account

No: the server works without sign-in

Capture and report bugs with automatic screen recordings and environment details. Create, view, and manage bug reports with full context.

How to connect

How to connect Jam to Claude

The server address to paste into Claude settings:

https://jam.run.tools

Open Claude (claude.ai or the desktop app).
Go to Settings → Connectors.
Click Add custom connector.
Paste the server address copied below into Remote MCP server URL and click Add.
In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect Jam to ChatGPT

The server address to paste into ChatGPT settings:

https://jam.run.tools

Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
Open Settings → Connectors and click Create.
Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect Jam to Cursor

The server address to paste into Cursor settings:

https://jam.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (15)

Raw names from tools/list. Only developers need these.

getDetails	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.
getNetworkRequests	Extract network activity logs captured during the Jam session. Returns HTTP/HTTPS requests including: URLs, methods (GET/POST/etc), status codes, headers, payloads, response times, and error details. Use filters to reduce output: statusCode (e.g., 500 or '5xx'), contentType (e.g., 'application/json'), host (e.g., 'api.example.com'), method (e.g., 'POST'), limit (max events). Essential for debugging API issues, failed requests, CORS problems, and performance bottlenecks.
getConsoleLogs	Retrieve browser console output captured during the Jam session. Includes JavaScript errors, warnings, info messages, debug logs, and stack traces. Use logLevel filter to focus on specific log levels (error, warn, info, log, debug). Critical for identifying runtime errors, debugging application state issues, and understanding the sequence of events leading to bugs.
getUserEvents	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.
getMetadata	Retrieve custom metadata set via the jam.metadata() SDK. Returns key-value pairs defined by the application developer, such as user IDs, app versions, feature flags, or any custom debugging context.
getScreenshots	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.
analyzeVideo	Extract user intents from a Jam recording. Identifies distinct user goals, issues, and feedback with detailed context including visual observations, interactions, and technical indicators.
getVideoTranscript	Retrieve the speech transcript (captions) from a video Jam recording in WebVTT format with timestamps. Only available for video Jams where the microphone was enabled during recording. Use this to understand what the user said while recording the bug report.
fetch	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.
search	Search for a Jam by extracting a UUID from a query string, jam.dev URL, or pasted text and returning matching Jam metadata.
listJams	List Jam bug reports with filtering and pagination. Search by text, filter by type (video/screenshot/replay), folder, author, URL, or creation date. Returns Jam metadata including title, author, folder, and timestamps. Use this to find specific Jams or browse the team's bug reports.
listFolders	List folders in the team with optional search and pagination. Returns folder metadata including name, short ID, Jam count, and timestamps. Use this to discover available folders for organizing Jams.
listMembers	List team members with optional search and pagination. Returns user metadata including name, email, and role. Use this to find users for filtering Jams by author.
createComment	Add a new comment to a Jam bug report. The comment body supports Markdown formatting. Use this to add notes, analysis results, or follow-up information to a Jam.
updateJam	Update a Jam bug report. Currently supports moving Jams between folders. Use folder name, folder ID, folder short ID, or "root" to move to the root level.