mcpField
J
Jam

Jam

Remote
jam.devDeveloper Tools11Updated today

About Jam

Jam skills help coding agents inspect screen recordings, diagnose issues, demonstrate fixes, and create end-to-end tests. They use Jam recordings that combine logs, network requests, user actions, and frames as evidence.

Key features

  1. 01Read recordings, logs, and user steps
  2. 02Analyze root causes using evidence
  3. 03Record working changes and return a link
  4. 04Annotate problem areas in screenshots
  5. 05Generate end-to-end tests from recordings

Use cases

  1. 01Investigate errors captured in a Jam
  2. 02Share a fix demonstration with a pull request
  3. 03Mark problem areas in a screenshot
  4. 04Turn a user flow into a regression test

MCP support

jam-fix and jam-to-e2e can read recordings through the Jam MCP server or Jam CLI; the plugin also connects to the Jam MCP server.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.jam.dev/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

Jam

Jam skills

Skills that make coding agents show their work: read a Jam, prove a change, point at the problem, test a flow.

skills.sh CI MIT


npx skills add jamdotdev/skills

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.

A Jam is a recording of what happened on screen, with the console logs, network requests and user actions attached, on one link. A bug report, a demo, a walkthrough of a flow. These skills teach your agent to read one, and to make one.

Skills

  • jam-fix: "Fix this jam.dev link." Reads the recording's console errors, failed requests, user steps, frames and transcript, then writes the root cause with evidence. Changes code only when you ask.
  • jam-proof: "Record a Jam showing it works." Records the change working and hands back a Jam link for the pull request, with console and network attached. Headless Chrome by default: it records the page, not your screen.
  • jam-annotate: "Mark what's broken and file it." Turns a screenshot into a Jam that points at the problem: boxes, arrows, notes, redactions and blurs, with the retina math done right.
  • jam-to-e2e: "Write an e2e test for this Jam." Turns a Jam into a test in your own runner and language, with first-class guidance for Playwright and tester-army/e2e. A Jam of a flow becomes a test that guards it. A Jam of a bug becomes a failing test, so the fix has something to turn green.

Requirements

Every skill needs a free Jam account. jam-fix and jam-to-e2e read a Jam through the Jam MCP server or the Jam CLI; jam-proof and jam-annotate create Jams, which needs the CLI. Install the CLI from jam.dev/cli; a skill signs in when it needs it. In CI or a cloud agent, set JAM_TOKEN to a personal access token. Window and display capture in jam-proof need macOS or Linux (X11); its default, recording a headless browser, needs only Chrome.

Install as a plugin

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

Claude Code
/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:

ln -s /path/to/skills ~/.cursor/plugins/local/jam
Codex
codex plugin marketplace add jamdotdev/skills
codex 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
copilot plugin marketplace add jamdotdev/skills
copilot plugin install jam@jam-plugins
Gemini CLI
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 the MCP server can do, and permissions: docs/plugin.md.

Contribute

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


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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.