---
title: "Jam | Console logs, network requests, and more"
image: "https://cdn-jam-screenshots.jam.dev/9d03db1ca0c33c65c1c1cf2c9986524f/screenshot/1c244c08-73ba-4c1a-b808-e7be5b0bb9f8.png"
url: "https://jam.dev/c/1c55e24f-e309-492a-9378-bb2cc2766564"
capturedOn: "https://www.figma.com/proto/5gMgOeLThBaTHkGemDhXkc/Standard-Template?page-id=4%3A3&type=design&node-id=281-6770&viewport=-781%2C182%2C0.25&t=gC0ER1d43XU0gZnZ-1&scaling=min-zoom&starting-point-node-id=4%3A728"
type: "video"
browser: "Chrome 121.0.6167.139"
os: "Mac OS (arm) 10.15.7"
screen: "1440x788"
country: "IT"
timezone: "Europe/Rome"
author: "Chiara Viganò"
date: "2024-02-01T16:50:47.699Z"
---

## Signals

3 interactions

## Not in this document

This is the summary tier. The captured events — console logs, network requests, user actions, and video frames — are not here: reading them needs filters, paging, and auth, so they live behind the Jam MCP server and CLI. Start at `getDetails`.

MCP: `https://mcp.jam.dev/mcp` (setup: https://jam.dev/docs/jam-mcp). CLI: `curl -fsSL https://native.jam.dev/install | bash` (https://jam.dev/docs/cli).