Introduction
The Jam.dev integration with Hatz brings powerful bug analysis and debugging capabilities directly into your AI-powered workflows. Jam.dev is a screen recording and bug capture tool that automatically collects all the technical context a developer needs to investigate and fix an issue — including console logs, network requests, user click events, error details, and more — the moment a recording is made.
By connecting Jam.dev to Hatz, you can ask Hatz to review a Jam session, analyze what went wrong, and help you triage, debug, or document issues — all without manually copy-pasting stack traces or switching between windows. Whether you're a developer investigating a bug, a QA analyst reviewing a test session, or a product manager triaging customer-reported issues, this integration saves significant time and context-switching.
Key benefits include:
Instantly pull full debugging context (logs, network calls, user events) from any Jam link into Hatz
Use AI to triage, root-cause, and document bugs faster
Eliminate manual reproduction steps — let Jam's recordings do the talking
Works seamlessly in both chat conversations and automated workflows in Hatz
How the Integration Works
The Jam.dev integration uses the Jam MCP (Model Context Protocol) server — a secure, remote connection that lets Hatz talk directly to Jam.dev's API on your behalf.
When you share a Jam link in a Hatz conversation or workflow, Hatz uses your personal access token to connect to https://mcp.jam.dev/mcp and retrieve the full debugging data associated with that recording. This includes the session details, console logs, network requests, user interactions, screenshots, video transcripts, and any custom metadata attached to the Jam.
The integration is per-user — each person in your team who wants to access Jam data through Hatz needs to set up their own connection using their own Jam personal access token. Your data is scoped to the Jam workspace associated with the token you create.
Getting Started
Prerequisites
Before setting up the integration, make sure you have:
An active Jam.dev account with access to a Jam workspace
At least one existing Jam recording to test with
Access to the Hatz platform with permission to manage connections
Step 1: Generate a Personal Access Token in Jam.dev
Hatz authenticates with Jam.dev using a Personal Access Token (PAT). Follow these steps to create one:
Log in to your Jam.dev account at jam.dev
Select your Workspace name in the top left and then click on Settings
Select MCP on the left menu and then select "+ Create Key" in the top right
Fill in the following details:
Name — Give the token a descriptive label (e.g., "Hatz")
Expiration — Choose how long the token should be valid:
Scopes — Select the permissions you need:
mcp:read— Allows Hatz to view Jam details, logs, events, and network requestsmcp:write— Allows Hatz to move Jams between folders and add comments
Click Create
Copy your token and save it in a safe place. This will be used in hatz for the integration
Step 2: Configure the Jam Integration in Hatz
Once you have your personal access token, you can connect Jam.dev to Hatz:
Login to Hatz, select Workshop at the top and then select Connections on the left menu
Find Jam in the list of available integrations and click Add
Enter your Jam Personal Access Token that you copied in Step 1
Click Connect
Confirm Jam is showing as connected in Hatz
Tools Available After Integration
Once the integration is set up, Hatz gains access to the following tools when working with Jam sessions:
Tool | Description |
getDetails | Get a quick snapshot of a Jam — who made it, what happened, and a summary of the issue |
getConsoleLogs | Retrieve console logs from a Jam, with filters for log level and result limits |
getNetworkRequests | List all network requests captured in a Jam as JSON, filterable by status code, content type, host, and more |
getScreenshot | Access every screenshot captured in a screenshot-type Jam |
getUserEvents | Review each click, input, and page navigation event in plain language |
getMetadata | Read custom key-value metadata (e.g. user IDs, app versions, feature flags) set via the Jam SDK |
getVideoTranscript | Get the spoken transcript from a video Jam where the microphone was enabled |
analyzeVideo | Analyse a Jam video recording to extract insights, detect issues, and provide structured feedback |
listJams | Search and filter Jams by text, type, folder, author, URL, or date |
listMembers | Browse team members in your Jam workspace |
listFolders | Browse available folders in your Jam workspace |
createComment | Add Markdown-formatted comments to a Jam |
updateJam | Move Jams between folders |
Jam Reference Guides
Below is Jam documentation that covers creating a PAT and their MCP functionality.