Skip to main content
Book a demo

Connect Jam to Claude

Give Claude governed access to Jam’s 15 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Claude setup guide

Set up

Add Jam to Claude in four steps

Admins approve the server once. Everyone in Claude then gets it through the same governed connection.

  1. 1

    Approve Jam in Runlayer

    Add Jam from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Claude to Runlayer

    Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, Jam’s 15 tools show up in Claude’s own tool list.

    Claude setup guide
  3. 3

    Sign in to Jam

    Sign in the way Jam requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Jam from Claude

    Jam’s approved tools appear in Claude. Every call is checked against policy and recorded.

Tools

15 Jam tools in Claude

Runlayer policy decides which of these Claude users can call. 13 read data only.

  • Get Jam bug report details and metadata

    Retrieve comprehensive metadata and details for a specific Jam bug report.

  • Get network activity and HTTP request logs

    Extract network activity logs captured during the Jam session.

  • Get browser console output and javascript logs

    Retrieve browser console output captured during the Jam session.

  • Get user interaction timeline and events

    Access the complete timeline of user interactions captured in the Jam.

  • Get custom Jam metadata

    Retrieve custom metadata set via the jam.metadata() SDK.

  • Get visual screenshots and image attachments

    Retrieve visual screenshots and image attachments from screenshot-type Jams.

  • Analyze video recording

    Extract user intents from a Jam recording.

  • Get video transcript

    Retrieve the speech transcript (captions) from a video Jam recording in WebVTT format with timestamps.

See all 15 Jam tools

Control

What Runlayer can see and stop in Claude

Some controls apply to every client at the gateway. Others depend on what Claude exposes to Runlayer.

  • Gateway policy (available)

    Every Jam call from Claude passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Claude as the client, the tool, and the policy and scanner decisions.

  • Anthropic inference hooks (available)

    With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).

  • Compliance API import (available)

    Anthropic Compliance API imports Claude web and desktop chats for review.

  • Managed browser extension (available)

    Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude prompt before Anthropic runs it, which stops the whole request rather than one tool call.

  • Block output after it runs (available)

    Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.

  • Redact output in place (not available)

    Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination