Automatic bug context capture
Jam automatically records the console, network activity, device and browser metadata, backend tracing, and user actions so the report includes debugging context without manual note-taking.
Jam is a browser-based bug reporting tool that captures screen recordings and debugging context so teams can share issues quickly and get back to work. Jam MCP sends recording context into supported AI coding tools.
Jam is a bug-reporting tool that helps people capture issues quickly, share them with the right context, and return to work. The site positions it as a browser-based workflow that is as easy as taking a screenshot, with automatic collection of the technical details engineers usually need to debug.
It supports bug capture for product, QA, support, and engineering teams, and it also offers Jam MCP, which lets a Jam recording flow into supported AI coding tools with video, events, logs, errors, and network requests attached. Pricing pages show Free, Team, and Enterprise options, plus a separate free offer for open-source projects.
Jam automatically records the console, network activity, device and browser metadata, backend tracing, and user actions so the report includes debugging context without manual note-taking.
Create an instant replay of what just happened, which helps teams review the path to a bug without asking the reporter to reconstruct it later.
Add annotations, blur sensitive details, edit the capture, and share the result as a link that the engineering team can open right away.
Connect Jam with tools shown on the site, including Jira, Linear, Slack, GitHub, GitLab, Sentry, Notion, ClickUp, Asana, Azure, and Figma, so reports fit into existing handoff flows.
Use Jam MCP to pass the full recording context into supported AI coding tools such as Claude Code, Cursor, VS Code, Windsurf, and ChatGPT connectors.
Pricing and plan pages show support for recording limits, AI summaries, access controls, webhooks, team collaboration, and security features such as SAML/SSO and audit logs on higher tiers.
QA can capture a bug with the screen recording, console output, network activity, and user actions in one link, reducing the need to rebuild the problem manually for engineering.
Support teams can send customers or teammates a Jam link that includes the relevant page behavior and debugging data, making follow-up easier than a plain text description.
Product and engineering teams can review an instant replay of what happened, then share annotations or markup to clarify the failure path before work starts.
Developers can paste a Jam link into a supported MCP client and have the recording context loaded into their AI assistant for debugging or implementation planning.
Open-source maintainers can use the dedicated OSS offer to capture and share issues while keeping the reporting workflow lightweight for contributors.
Jam is designed to be used after you install the browser extension and start a recording. The docs say you need a Jam recording before an agent can use Jam MCP, and that the extension is used to capture the screen, voice, and context.
The pricing page shows a Free plan, a Team plan, and an Enterprise plan. The Free plan is for getting started, Team adds higher limits and more AI summaries, and Enterprise adds SAML/SSO, audit logs, and priority support.
Jam can capture console logs, network requests, user actions, backend tracing, device and browser info, screenshots, annotations, and replay. The exact set depends on how you record and which features or plan you use.
The site shows integrations and workflows with tools such as Jira, Linear, Slack, GitHub, GitLab, Sentry, Notion, ClickUp, Asana, Azure, and Figma. The MCP docs also describe sending Jam context into Claude, Cursor, VS Code, Windsurf, ChatGPT, and other supported clients.
The source pages show Jam for browser-based bug capture, Jam MCP for feeding recordings into AI coding tools, and a Jam OSS offer for open-source projects. The pages do not spell out every limitation, so fit should be checked against your recording, integration, and workflow needs.