# Jam MCP server

> Load Jam bug recordings, with console logs, network requests and user events, into your AI coding agent.

- Listing: https://mcp.tc/i/jam
- Connect: use the server's own URL `https://mcp.jam.dev/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Developer Tools](https://mcp.tc/c/developer-tools)
- Vendor: Jam
- Homepage: <https://jam.dev/docs/jam-mcp>

## About

Jam MCP connects your coding assistant to Jam bug recordings. Paste a Jam link and the agent can read the recording's details, console logs, network requests and user events. The docs also list tools for searching and browsing Jams, commenting and reacting, and organizing Jams and folders.

It runs as a hosted streamable HTTP endpoint at https://mcp.jam.dev/mcp. You sign in to Jam through OAuth and allow access to your workspace. It works with clients such as Claude, Cursor, VS Code, Windsurf, ChatGPT and OpenCode. Recordings are made with the Jam Chrome extension.

## What it can do

- Open a Jam link and read who made it and what happened
- Fetch console logs with log level, limit and cursor filters
- List network requests from a recording as JSON
- Search and browse Jams in your workspace
- Comment and react on Jams
- Organize Jams and folders

## Example prompts

- "Here is a Jam link. Read the console errors and suggest a fix."
- "Check the network requests in this Jam and find the failing call."
- "Summarize the repro steps in this Jam and plan a fix."
- "Triage the feedback in these Jam links and group it by theme."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http jam https://mcp.jam.dev/mcp
```

2. Start Claude Code, type `/mcp`, pick **jam** and choose **Authenticate**. A browser window opens for the Jam sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Settings → Connectors** and click **Add custom connector**.

2. Name it **Jam** and paste this URL:

```url
https://mcp.jam.dev/mcp
```

3. Click **Add**, then **Connect**, and sign in when Jam asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Jam&connectorUrl=https%3A%2F%2Fmcp.jam.dev%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://mcp.jam.dev/mcp` and click **Add**.

3. Click **Connect** and sign in when Jam asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.

2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.

3. Paste `https://mcp.jam.dev/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Jam to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=jam&config=eyJ1cmwiOiJodHRwczovL21jcC5qYW0uZGV2L21jcCJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "jam": {
      "url": "https://mcp.jam.dev/mcp"
    }
  }
}
```

Cursor shows **Needs login** next to the server. Click it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=jam&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.jam.dev%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"jam","type":"http","url":"https://mcp.jam.dev/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "jam": {
      "type": "http",
      "url": "https://mcp.jam.dev/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "jam": {
      "serverUrl": "https://mcp.jam.dev/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add jam --url https://mcp.jam.dev/mcp
codex mcp login jam
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.jam]
url = "https://mcp.jam.dev/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http jam https://mcp.jam.dev/mcp
```

Then, inside Gemini CLI, run `/mcp auth jam` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "jam": {
      "type": "http",
      "url": "https://mcp.jam.dev/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.jam.dev/mcp`.

## Details

- Last checked: 2026-10-03 (reachable, asks for credentials)
- Listed: 2026-10-03
- Updated: 2026-10-03

---
Source: https://mcp.tc/i/jam (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report