# Jam

Brings Jam recordings into an AI coding agent, including video, user actions, console output, and network traffic. Use it to investigate bugs and turn flows into tests.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 11
- Author: jamdotdev
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/jamdotdev/skills
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/mcp/jam

## What it does

Jam gives an agent a recording as working context: what appeared on screen, which actions the user took, console messages, and network requests. The agent can inspect that evidence, trace a failure to its likely cause, and turn a recorded flow into an end-to-end test.

The MCP connection uses `https://mcp.jam.dev/mcp`. It supports reading Jams for debugging and test creation, while making new recordings uses the Jam CLI. A free Jam account is required.

Cloud agents and CI jobs need `JAM_TOKEN` set to a personal access token. Without a Jam account, the server cannot provide access to recordings.

## Requirements
- Remote server: `https://mcp.jam.dev/mcp`

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http jam https://mcp.jam.dev/mcp
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add jam --url https://mcp.jam.dev/mcp
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "jam": {
            "url": "https://mcp.jam.dev/mcp"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "jam": {
            "type": "http",
            "url": "https://mcp.jam.dev/mcp"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http jam https://mcp.jam.dev/mcp
```

## When to use it
- trace a UI failure through console and network evidence
- identify the root cause behind a recorded bug
- turn a recorded user flow into an e2e test
- check a code change against a captured scenario

## Example prompts
- Inspect this Jam, trace the failure, and tie the diagnosis to its console errors and network requests.
- Turn the flow in this Jam into an e2e test using the runner already used by this project.
- Review this recording and list the user actions that the test must reproduce.

## Similar
- [game-jam](https://affpapa.org/en/nevibecode/skills/game-jam.md) — skill · 6000 installs
- [game-jam-mode](https://affpapa.org/en/nevibecode/skills/game-jam-mode.md) — skill · ★ 47
- [REA](https://affpapa.org/en/nevibecode/mcp/rea.md) — MCP server · ★ 392262
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33989
- [World Monitor](https://affpapa.org/en/nevibecode/mcp/world-monitor.md) — MCP server · ★ 89609
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81163
- [Front-End Checklist](https://affpapa.org/en/nevibecode/mcp/front-end-checklist.md) — MCP server · ★ 74569
- [Scrapling MCP Server](https://affpapa.org/en/nevibecode/mcp/scrapling-mcp-server.md) — MCP server · ★ 89899

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md