Jam MCP

Jam MCP connects your agent to Jam, where teams record bugs and feedback with their full technical context. Paste a Jam link and your agent loads the recording's details, console logs, network requests, user events and what was on screen, so it can go from bug to fix without copy-pasting. What you can do with it - Read a Jam: who made it and what happened, console logs, network requests (filtered by status code, host or method), each click, input and page change, custom metadata, screenshots, video frames, the spoken transcript and chapters - Search Jams across your workspace by text, author, folder, page URL, linked issue, browser, date and more - Comment on a Jam and mention a teammate, and react to comments - Rename Jams, rewrite their descriptions and file them into folders - Create and manage Recording Links, and list your connected recording domains How it connects It's a hosted server at https://mcp.jam.dev/mcp. Jam documents setup for ChatGPT (as a plugin), Claude (as a connector), Cursor, VS Code, Windsurf and OpenCode, and its plugin for Claude Code, Codex, GitHub Copilot CLI and Gemini CLI connects the server and adds Jam's skills. You sign in to Jam in your browser the first time; for CI or other headless setups, use a personal access token as a Bearer header instead. Good to know - It sees only the Jams your account can already see, and you can revoke access any time in Jam's Settings, under MCP. - Deleting a Jam, a comment or a folder is permanent: Jam has no trash. - Creating a folder or a Recording Link can upgrade you from Viewer to Creator when your workspace allows it, which can change seat billing. - Some tools use Google's Gemini; Jam says it opts out of training on customer data. - The video tools and screenshots aren't available for Instant Replay Jams.