Jam
Jam captures a bug report with the console logs and network requests attached. Antimetal reads those recordings to connect a front-end report to the back-end error behind it.
What Antimetal does with Jam
- Read bug recordings with console logs and network requests
- See the exact reproduction steps a user hit
- Inspect the failing request from the user's browser
- Tie a front-end report to a back-end error
Connecting Jam
Go to Integrations in the Antimetal dashboard and find Jam.
Click Connect and follow the prompt. Depending on the tool this is either an OAuth handoff or a read-only credential you generate in Jam and paste into Antimetal.
Once Jam shows as connected, Antimetal begins pulling from it during investigations. No further configuration is required.
Permissions and access
Antimetal connects over MCP with read-only access and performs no write operations. The exact scopes depend on the credential you issue in the vendor tool — grant read access only.
All tenant data is processed in isolated environments. See security and compliance for details.
Related integrations
Need help?
Contact us via Slack or at support@antimetal.com.