Jam

dev.jamPublished by jam.devOfficial publisherv1.36.3Updated Nov 3, 2026

Jam recordings (video, console, network) as context and proof of work for your coding agent.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

Jam's hosted MCP server (mcp.jam.dev), published by jam.dev; OAuth sign-in required; Streamable HTTP.

No AI overview yet: these facts come from the registry entry and the server itself.

Publisher
jam.dev
Endpoint
mcp.jam.dev
Last checked

Installation

In SourceWeft

  1. Open Jam in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.jam%2Fjam/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

README

[Jam]

Jam skills

Your agent sees what you saw, and shows you what it did.

[skills.sh] [CI] [MIT]


bash
npx skills add jamdotdev/skills

Then paste a Jam link and say what you want:

  • "fix this https://jam.dev/c/…"
  • "do what I said in this jam"
  • "make a ticket for this jam"
  • "record a jam showing it works"

A Jam is a screen recording or screenshot with the console logs, network requests and user actions attached, on one link. You'd record one for a bug report, a feedback walkthrough or a demo. These skills let your agent read a Jam, and record its own when it's done, so you check the result by watching it.

Works with Claude Code, Cursor, Codex, GitHub Copilot, Gemini CLI, OpenCode and every agent skills.sh supports. Add --skill jam-fix to install one skill.

Skills

You don't need to remember these names. Paste a Jam link, say what you want, and your agent picks the skill.

Give your agent a Jam

  • jam: "Take a look at this jam." For a link with no instructions. It reads the Jam and picks the skill below that fits.
  • jam-fix: "Fix this jam." Finds the root cause from the errors, failed requests and steps in the recording, and shows the evidence. It changes code only when you ask.
  • jam-to-tasks: "Do what I said in this jam." Turns your feedback into a numbered to-do list, each item tied to the moment you said it, then works through it.
  • jam-to-e2e: "Write a test for this jam." Writes an end-to-end test with your project's own test setup. A Jam of a bug becomes a test that fails until the fix lands.
  • jam-to-ticket: "Make a ticket for this jam." Files it in Linear, GitHub Issues or Jira with the steps, a frame from the recording and the errors, unless a ticket already exists.
  • video-to-jam: "Split this recording by bug." Turns an MP4, a Loom download or a long call into one Jam per issue.

Get a Jam back

  • jam-proof: "Record a jam showing it works." Records the change working and gives you a Jam link for the pull request.
  • jam-annotate: "Mark what's broken and share it." Draws boxes, arrows and notes on a screenshot, blurs anything private, and shares it as a Jam.
  • jam-proof-table: "Give me the jams for each fix." After a batch of work, one table: each claim, whether it works, and the Jam that shows it.

Set up Jam

  • jam-setup: "Set up jam." Installs the Jam CLI, signs you in, connects Jam MCP, installs these skills and runs jam doctor, in that order. It asks once whether to set up this project or every project on your machine.

Make a video

These need no Jam account. With the Jam CLI, a video can become a Jam link to comment on.

  • record-demo: "Record a demo of this feature." Plays the flow in a browser at human pace and renders a narrated 1440p video, with the camera moving only where the script says.
  • add-voiceover: "Add a voiceover to this video." Writes a script for the ear, voices it line by line and lays each line on the moment it describes, with a subtitle file.
  • record-terminal-proof: "Record proof that the migration ran." Records the commands and renders a GIF that plays inline on the pull request.

Requirements

  • A free Jam account, for every skill except the three video skills.
  • The Jam CLI. Say "set up jam" and jam-setup walks you through it. A skill signs in when it needs to. jam, jam-fix and jam-to-e2e can read a Jam through Jam MCP instead, the Model Context Protocol (MCP) server the plugin connects.
  • For video-to-jam: ffmpeg and a local transcriber such as Whisper.
  • For record-demo: agent-browser 0.38.1 or later, ffmpeg and Node 22 or later, with no npm packages. Its narration comes from add-voiceover.
  • For add-voiceover: ffmpeg and Node 22 or later, with no npm packages. An ElevenLabs key or the free Kokoro model (Python 3 and uv) gives a natural voice; without either, it uses the macOS voice.
  • For record-terminal-proof: asciinema 3 and agg. On Windows, use WSL.
  • In CI or a cloud agent: a personal access token in JAM_TOKEN.
  • For jam-proof: recording a web page needs only Chrome. Recording a window or the whole screen needs macOS or Linux (X11).

Install as a plugin

The plugin installs every skill, connects Jam MCP and updates itself. Use the plugin or npx skills add, not both, or the agent sees every skill twice.

Claude Code
shell
/plugin marketplace add jamdotdev/skills/plugin install jam@jam-plugins

Skills load as /jam:jam-fix, /jam:jam-proof, and so on. To test a checkout, run claude --plugin-dir /path/to/skills.

Cursor

Open Customize in the sidebar, search for Jam, and click Install.

To test a checkout, link it into the local plugin folder and run Developer: Reload Window:

bash
ln -s /path/to/skills ~/.cursor/plugins/local/jam
Codex
bash
codex plugin marketplace add jamdotdev/skillscodex plugin add jam@jam-plugins

Start a new session, complete the OAuth prompt, and run /mcp to check the connection. To test a checkout, pass its path to marketplace add.

GitHub Copilot CLI
bash
copilot plugin marketplace add jamdotdev/skillscopilot plugin install jam@jam-plugins
Gemini CLI
bash
gemini extensions install https://github.com/jamdotdev/skills

Run /mcp auth Jam once to sign in. To test a checkout, run gemini extensions link /path/to/skills.

Sign-in, tokens, what Jam MCP can do, and permissions: docs/plugin.md.

Contribute

Bug in a skill, or a skill you want? Open an issue. Pull requests are welcome, and CONTRIBUTING.md is short.

jam.dev · Jam MCP · Jam CLI · Dev Utils · Changelog · MIT

Source: README.md at commit 37b3a72

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v1.36.3LatestNov 3, 2026
  2. v1.27.1Oct 22, 2026
  3. v1.23.2Oct 18, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts