Claude Jam connectorWhat Claude can do in your Jam account.
The Claude Jam connector lists 6 tools on its directory sheet. 5 read a bug recording, 0 write, and 1 has no official description. Below: what Claude pulls out of a Jam link, what stays out of reach, and why Jam's own docs list many more tools.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can open a Jam
A tester records a bug with Jam and drops the link in a ticket. Without the connector, someone replays the video, copies console errors by hand and retypes the steps. With it, you paste the link into a conversation and Claude reads the capture itself: who filed it, the console output, the web requests, every click. You ask what broke, and the answer comes from the recording rather than from memory.
Spot the failing call. A checkout spinner never stops. getNetworkRequests returns the requests captured during the session, and you can ask Claude to keep only one host or one status code. Bodies come back for errors unless you ask for all of them.
Read the console without opening the browser tools. getConsoleLogs pulls the log lines out of the Jam, filtered by level, so a pile of warnings doesn't hide the one error that matters.
Rebuild the steps to reproduce. getUserEvents turns each click, input and page change into plain sentences, and getDetails tells Claude who made the recording and what happened before it digs deeper. On a video Jam, analyzeVideo adds a structured review of the problems it spots on screen.
Now the part the sheet doesn't spell out. By default, its tool list only reads: no comment, no rename, no deletion. Jam documents tools for those, but they aren't on the sheet, so this page leaves them out. Video analysis skips Instant Replay Jams. And nothing runs on its own: Claude only opens a Jam when you give it a link in a conversation. Filing a ticket the moment a recording lands is automation work, a different job, and the Integrations hub gathers that side.
The vocabulary in one minute
Five words you will meet while plugging Jam into Claude.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs as it answers; the directory lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use. Given once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it finishes something that changes your account, shown in the conversation when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service.
Plug Jam into Claude in three steps
- 01
Find Jam in Claude's settings
Open Claude's settings, go to Customize, then Connectors, and look for Jam in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Jam in the window Jam opens itself. If the link breaks later, hit Disconnect and plug it back in: that is the documented fix.
- 03
Read the authorization screen
Read the screen before you accept. It belongs to Jam, not to Claude, and it decides what the access covers. You can also withdraw that access later from your Jam account itself.
The 6 tools, sorted by what they do
Jam gives Claude 6 tools: 5 that read your account, 0 that change something in it, and 1 no official source describes.
Two groups here: what Claude reads, and what no official source describes. Names stay exactly as Claude shows them.
- 5 read
- 1 not documented
What Claude reads (5)
5 toolsFive tools that look inside a recording without changing it.
getDetails
A first look at the recording: who created it, what happened during the session, and which other tools are worth calling next.
getConsoleLogs
Brings back the console lines recorded in the Jam. You can narrow them by log level, cap how many arrive, and page through long sessions, so the noise stays out of the chat.
getNetworkRequests
Lists each web request captured in the session. Claude can filter by status code, content type, host or method, and fetch response bodies for failures only, or for everything.
getUserEvents
Turns every click, typed input and navigation of the recording into readable sentences. You get the exact path the person took. No video to scrub through.
analyzeVideo
Reviews the video of a Jam and returns structured feedback: what it noticed, which issues show up on screen, and the insights it draws from them.
Not documented (1)
1 toolThe directory publishes this name and nothing else. No official text says what it does, and a name is not enough to guess.
getScreenshot
The directory lists this name and stops there. Jam's documentation describes a tool spelled getScreenshots, with a final s; the names differ, so this page does not treat them as one and says nothing more.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before each action it carries out on an account for you. The request shows up in the conversation, right when it matters.
On Team and Enterprise, workspace owners decide whether members may let some actions through without being asked again. They can also cap what a connector may do for the whole organization, keeping reading open and closing writing, for instance. Nobody gets around that from their own account. Jam adds its own guardrail: the connector mirrors your Jam permissions and opens nothing you can't already see in the web or mobile app.
Which plans include it
Out of 819 sheets in the official directory, none shows availability plan by plan. That answer isn't published anywhere, connector by connector: it's a real hole in the catalogue, not a gap in our research.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization first. For the current state on your account, the Jam sheet in the official directory is the place to check.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you; nothing fires when a new recording arrives in your workspace.
The tool list is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The partner badge isn't a security audit either, and Anthropic states on every sheet that it doesn't choose the tools a publisher exposes or guarantee they behave as described. Only plug in what comes from a publisher you know. This connector is documented by its publisher alone: no Claude help article covers it, so every specific limit below comes from Jam's own guide.
How many tools does the Jam connector give Claude?
- Claude directory sheet ↗October 2026Six tools, all for consulting a recording, with the screenshot tool spelled getScreenshot.
- Jam MCP documentation ↗September 202634 tools, including comments, renaming, folders and deletion, with the screenshot tool spelled getScreenshots.
What this page followsBoth are current and describe different things: the sheet shows what the directory publishes, the docs show what Jam's service can do. The list Claude displays on your own account after connecting is what counts. This page covers only the six tools on the sheet.
Need help connecting Jam to Claude?
A person reads every message.