English Français العربية

Jam

Registre officiel Outils de développement

Jam recordings (video, console, network, logs) as context for your coding agent.

Code source Site web Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http jam 'https://mcp.jam.dev/mcp'
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "jam": {
            "type": "http",
            "url": "https://mcp.jam.dev/mcp"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. Jam skills
  2. Skills
  3. Requirements
  4. Install as a plugin
  5. Contribute

Jam skills

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

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

Questions fréquentes

Qu'est-ce que Jam ?

Jam recordings (video, console, network, logs) as context for your coding agent.

Comment installer Jam ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http jam 'https://mcp.jam.dev/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Jam ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

Jam est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Jam ?

Il est publié par jamdotdev. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.