How to connect Jam to OpenClaw
Connect Jam to OpenClaw with ClawLink: paste your Jam key once and 16 tools work from chat. No MCP server to run, nothing stored on your machine.
JamAPI KEYMCPJam helps teams capture, inspect, organize, and collaborate on browser bug reports and recordings through its hosted MCP API.. Once connected, OpenClaw can read and act on Jam from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Jam access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Jam setup: install one ClawHub skill, connect Jam in the browser, and OpenClaw can call real Jam actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Jam.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Jam
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Jam?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Jam in the ClawLink dashboard — paste your Jam API key once.
Verify the connection by asking OpenClaw:
Use Jam to analyze video and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Jam is connected in the dashboard, that agent calls the same 16 Jam tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Jam MCP for OpenClaw
Looking for a Jam MCP server for OpenClaw? ClawLink connects Jam to OpenClaw and exposes 16 Jam tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Jam integration works the same way.
What the OpenClaw Jam integration can do
16 Jam tools are ready for OpenClaw once the account is connected.
All 16 Jam tools for OpenClaw
| Tool | What it does |
|---|---|
Analyze video jam_analyze_video | Extract structured user goals, reported issues, feedback, visual observations, interactions |
Get console logs jam_get_console_logs | Get captured browser console errors, warnings, information, debug output, and stack traces from |
Get jam details jam_get_jam_details | Get the core details and debugging context for a Jam |
Get jam metadata jam_get_jam_metadata | Get custom application debugging context attached through the jam.metadata() SDK, such as user |
Get network requests jam_get_network_requests | Get captured HTTP requests and WebSocket frames from a Jam, with filters for failures, hosts |
Get recording link jam_get_recording_link | Get one Recording Link's settings and submitted-Jam count by public ID |
Get screenshots jam_get_screenshots | Get screenshots and image attachments from a screenshot-type Jam for visual inspection |
Get user events jam_get_user_events | Get the chronological user interaction timeline from a Jam, including clicks, inputs |
Get video frames jam_get_video_frames | Get still frames from a video Jam as an overview grid, exact timestamps, or an evenly sampled |
Get video transcript jam_get_video_transcript | Get the timestamped WebVTT speech transcript from a microphone-enabled video Jam when |
List folders jam_list_folders | Browse or search one page of workspace folders and return their IDs, names, Jam counts, and |
List jams jam_list_jams | Search and browse workspace Jams by text, type, folder, author, source URL, or creation date |
List members jam_list_members | Browse or search one page of workspace members by name or email for author discovery and |
List recording domains jam_list_recording_domains | List the workspace's connected recording domains and whether each is verified to capture |
List recording link jams jam_list_recording_link_jams | List Jams submitted through one Recording Link, newest first |
List recording links jam_list_recording_links | List workspace Recording Links newest first, optionally including revoked links |
Try it: find the Jam tool you need
Browse the 16 Jam tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Jam to analyze video and walk me through the result in plain English.
Pull the relevant data from Jam, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Jam, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Jam, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Jam working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Jam API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Jam account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Jam. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Jam actions to the runtime in a format your agent can reliably use. | 16 tools for Jam are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Jam to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Jam in the browser, and the 16 tools above work from chat. There is no SDK and no config file, and the Jam key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Jam skill but can't call the tools
The ClawHub skill teaches OpenClaw about Jam, but the calls run through the ClawLink plugin and your connected account. Make sure Jam is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Jam from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Jam tools
Jam tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Jam call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Jam returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Jam has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Jam integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Jam: link your Jam account once in the browser and OpenClaw can call the Jam API through 16 ready-made tools — no custom code or token handling.
How do I add Jam to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Jam skill from ClawHub, then you click Connect in the dashboard to authorize Jam. OpenClaw calls the tools from the next message — no config files, and the Jam key you paste is stored server-side instead of in your environment.
How long does it take to connect Jam to OpenClaw?
About two minutes. Sign in, click Connect next to Jam in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Jam up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Jam working from chat.
OpenClaw installed the Jam skill but can't call the tools
The ClawHub skill teaches OpenClaw about Jam, but the calls run through the ClawLink plugin and your connected account. Make sure Jam is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
GitHub tools
Manage repositories, issues, pull requests, and workflows
PagerDuty
Manage incidents, on-call schedules, and services
SafetyCulture
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.