Jam MCP Server

Provider-hosted MCP server that loads Jam bug recordings (video, console logs, network requests, user events) into AI coding agents.

Developer Tools by Jam.dev OAuth2 active

Connect (Remote Server) Docs

Overview

Jam is a bug reporting tool that captures screen recordings along with the technical context engineers need to reproduce and fix issues: console logs, network requests, user interactions, browser metadata, and a video of the session. The Jam MCP server, hosted by Jam.dev at https://mcp.jam.dev/mcp, exposes those recordings to AI agents like Claude Code, Cursor, VS Code, Windsurf, ChatGPT, Codex, and OpenCode.

Once connected, an agent can be pointed at a Jam URL (or asked to search the workspace) and pull the complete debugging context into its working memory. Tools include getDetails, getConsoleLogs, getNetworkRequests, getUserEvents, getScreenshot, getVideoTranscript, analyzeVideo, plus workspace operations like listJams, listFolders, listMembers, createComment, and updateJam.

Authentication is OAuth2: the first tool call triggers an approval flow that respects existing Jam workspace permissions. There is no self-hosted version. Users point their MCP client at the remote URL and authorize once.

Tools

Tool	Description
`getDetails`	Quick snapshot of a Jam with metadata and guidance on which other tools to call next.
`getConsoleLogs`	Retrieve console logs from the recording with optional level and limit filtering.
`getNetworkRequests`	List every network request captured during the Jam as JSON with filtering options.
`getScreenshot`	Return a screenshot from the Jam for visual inspection. Not available for Instant Replay Jams.
`getUserEvents`	Read each user click, input, and page navigation captured in the recording.
`getMetadata`	Custom key/value metadata attached via the jam.metadata() SDK.
`getVideoTranscript`	Spoken transcript of the recording in WebVTT format.
`analyzeVideo`	Run video analysis to detect issues in the recording. Not available for Instant Replay Jams.
`listJams`	Search Jams in the workspace by text, type, folder, author, URL, or date.
`listMembers`	Browse members of the Jam workspace.
`listFolders`	Browse folders in the workspace.
`createComment`	Add a Markdown comment to a Jam.
`updateJam`	Move a Jam between folders.

Setup Guide

Prerequisites

A Jam.dev account and at least one Jam recording (created via the Jam Chrome extension or iOS app)
An MCP-capable client (Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, ChatGPT, Codex, OpenCode)

The server is hosted by Jam at https://mcp.jam.dev/mcp. Auth is OAuth2, triggered on first tool call.

Claude Code

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

Cursor

Add to your mcp.json:

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

VS Code / Windsurf

Open the command palette (Cmd/Ctrl + P), run >MCP: Add Server, choose HTTP, paste https://mcp.jam.dev/mcp, name it Jam.

Codex

Add to ~/.codex/config.toml:

[mcp_servers.jam]
url = "https://mcp.jam.dev/mcp"

Claude Desktop

Add Jam via the Connector Directory and authorize your workspace.

After installation, the first tool call opens a browser window to complete OAuth2 authorization against your Jam workspace.

Use Cases

Hand an AI coding agent a Jam URL and have it read the console errors, failing network requests, and user click path to propose a fix
Triage a backlog of Jams by asking the agent to listJams filtered by date or folder and summarize the top issues
Generate a structured bug ticket (steps to reproduce, expected vs actual, stack trace) from a single Jam recording
Have the agent run analyzeVideo plus getVideoTranscript on a QA recording to identify regressions described verbally
Auto-comment on a Jam via createComment with the agent's root-cause analysis and link to a fix PR

Example Prompts

"Open this Jam and tell me why the checkout button doesn't work: https://jam.dev/c/..."
"List all Jams created in the last 7 days in the Bugs folder and summarize the top three issues"
"Pull the console logs and network requests from this Jam and find the failing API call"
"Read the video transcript from this Jam and turn it into a Linear ticket"
"Analyze this Jam, then post a comment with your root cause hypothesis"

Pros

Officially hosted and maintained by Jam.dev, no self-hosting required
Comprehensive coverage: video, console, network, user events, transcript, and workspace search in one server
OAuth2 with workspace permission inheritance, no API keys to manage
Works across most major MCP clients (Claude, Cursor, VS Code, Windsurf, ChatGPT, Codex, OpenCode)

Limitations

Requires an active Jam account and existing recordings, useless without the Chrome extension or iOS app capturing data
getScreenshot and analyzeVideo are not available for Instant Replay Jams
Remote-only, no self-hosted option for teams with strict data residency requirements

Alternatives

Sentry MCP: error and performance data from production rather than recorded sessions
LogRocket: session replay with a similar bug-context use case, though MCP support is more limited
Replay.io: time-travel debugging for recorded browser sessions, alternative recording approach