# How to connect Jam to Hermes Agent (paste one key, 16 tools) > Connect Jam to Hermes with ClawLink: paste your Jam key once and 16 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/jam Most guides for giving Hermes Agent Jam access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Jam setup: pair once in the browser and your always-on Hermes agent can act on Jam for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect Hermes to Jam. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Jam** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect jam # connect Jam (browser OAuth) npx -y @useclawlink/cli actions jam # list available actions npx -y @useclawlink/cli run jam --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect Jam in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Jam API key once. Verify the connection by asking Hermes: > Use Jam to analyze video and walk me through the result in plain English. ### Using a different agent? The Hermes 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: ```bash npx -y @useclawlink/cli login ``` `login` 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Jam MCP for Hermes Looking for a Jam MCP server for Hermes Agent? ClawLink connects Jam to Hermes Agent and exposes 16 Jam tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Jam integration](https://claw-link.dev/openclaw/jam) works the same way. ## What the Hermes Agent Jam integration can do 16 Jam tools are ready for Hermes Agent once the account is connected. ### All 16 Jam tools for Hermes | 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 | ## Example prompts **Analyze Video** > Use Jam to analyze video and walk me through the result in plain English. **Get Console Logs** > Pull the relevant data from Jam, summarize it in plain English, and point out anything that needs attention. **Get Jam Details** > Pull the relevant data from Jam, summarize it in plain English, and point out anything that needs attention. **Get Jam Metadata** > 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 Hermes Agent. 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 Hermes Agent 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Jam Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### 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. ### Is there a Hermes Agent Jam integration? Yes. ClawLink is the fastest way to connect Hermes to Jam: link your Jam account once in the browser and Hermes Agent can call the Jam API through 16 ready-made tools — no custom code or token handling. ### How do I connect Jam to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Jam in the dashboard and Hermes can use it 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 Hermes Agent? About two minutes. Sign in, click Connect next to Jam in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Jam working from chat. ### Hermes paired but still can't use Jam Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [Hermes GitHub integration](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services - [Connect SafetyCulture](https://claw-link.dev/hermes/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.