Connect Jam to Claude Cowork
Give Claude Cowork governed access to Jam’s 15 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Jam to Claude Cowork in four steps
Admins approve the server once. Everyone in Claude Cowork then gets it through the same governed connection.
- 1
Approve Jam in Runlayer
Add Jam from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Claude Cowork to Runlayer
Claude Cowork gets connector tools through the Runlayer Plugin. With direct tool listing turned on for your deployment, Jam’s 15 tools show up in Claude Cowork’s own tool list.
Claude Cowork setup guide - 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
Use Jam from Claude Cowork
Jam’s approved tools appear in Claude Cowork. Every call is checked against policy and recorded.
Tools
15 Jam tools in Claude Cowork
Runlayer policy decides which of these Claude Cowork 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.
Control
What Runlayer can see and stop in Claude Cowork
Some controls apply to every client at the gateway. Others depend on what Claude Cowork exposes to Runlayer.
Gateway policy (available)
Every Jam call from Claude Cowork passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude Cowork as the client, the tool, and the policy and scanner decisions.
Anthropic inference hooks (available)
Anthropic Inference hooks let Runlayer check Claude Cowork prompts before inference.
OTLP telemetry (available)
Claude Cowork can send supported OpenTelemetry events to Runlayer for observe-only session visibility.
Stop a call before it runs (available)
Runlayer can reject a Claude Cowork 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)
Runlayer cannot mask content in Claude Cowork. The gateway still applies policy to the call.
In Claude Cowork
- Cowork session data sent over OpenTelemetry is for monitoring only and cannot stop anything.
Frequently asked questions
Connect more