Jam MCP Server
Connect Jam to your AI agents with the Jam MCP server.
Updated
What is Jam MCP?
The Jam MCP server is a Model Context Protocol server that connects Jam to AI agents and assistants as a set of tools. With it connected, an agent can work with Jam (bug reporting for dev teams) directly — instead of you copying data in and out by hand.
It is a remote MCP server that uses OAuth, so you point your client at the server URL, authorize once, and the Jam tools become available to the model.
Connect the Jam MCP server
Connect Jam MCP to Claude Code
- 1
Add the server
Use `claude mcp add` with the Jam MCP server URL (or its `npx` command), following the official docs.
- 2
Authorize
Complete authentication (OAuth) so Claude Code can call the server.
- 3
Verify
Ask Claude to use a Jam tool to confirm the connection is live.
Connect Jam MCP to Cursor
- 1
Open MCP settings
In Cursor, go to Settings → MCP → Add new server.
- 2
Add Jam
Provide the Jam MCP server URL or command and complete authentication.
- 3
Test
Reference Jam from chat to confirm Cursor can reach the tools.
Sample use cases
A QA engineer captures a bug with full context in one click
Jam records the screen, console logs, network requests, and device info, then the agent files the bug in the issue tracker with all artifacts attached.
A product manager reviews incoming bug reports for prioritization
The agent pulls recent Jam reports, extracts severity signals (error count, affected users), and ranks them for the next triage meeting.
A frontend developer investigates a CSS rendering issue
The agent retrieves the Jam replay with DOM snapshots and console logs, pinpoints the failing CSS rule, and suggests a fix based on the browser version.
A support agent reproduces a customer-reported bug
Instead of asking the customer for steps, the agent pulls the Jam recording shared via support ticket and confirms the exact reproduction path.
An engineering manager tracks bug report volume by feature area
It groups Jam reports by URL pattern and component tag, producing a weekly heatmap of where bugs are concentrated in the product.
A release manager checks for regression bugs before deployment
The agent queries Jam for reports filed since the last release cut, cross-references with the changelog, and flags potential regressions.
A design reviewer checks visual consistency across browsers
It collects Jam screenshots from multiple browser sessions, compares rendering, and highlights layout discrepancies for the design team.
Using Jam MCP with Gamut
On Gamut, the Jam MCP server becomes a tool your agents use inside an automated, event-driven workflow — triggered by an event or a schedule, acting through Jam and your other connected MCP servers, with the connection managed by Gamut rather than a local config file.
Frequently asked questions
What is the Jam MCP server?
It is a Model Context Protocol server that exposes Jam to AI agents as tools so they can work with it (bug reporting for dev teams).
How do I connect the Jam MCP server?
Point your MCP client (Claude, Cursor, or Gamut) at the Jam MCP server URL and complete authentication (OAuth). See the official documentation for the exact URL and scopes.
Can I use Jam MCP with Gamut?
Yes — Gamut supports the Jam MCP server, so your agents can use it as a tool in automated, triggered workflows.
What is Jam?
Jam is a bug reporting tool that captures screen recordings, console logs, network activity, and device metadata in a single click, making it easy to file detailed bug reports.
Does Jam work with all browsers?
Jam offers a Chrome extension and supports Chromium-based browsers. It captures DOM, console, and network data specific to the browser session.
Can Jam integrate with issue trackers?
Yes. Jam integrates with Jira, Linear, GitHub Issues, Asana, and other trackers, letting you push bug reports with all captured context directly into your workflow.
How does the Jam MCP server connect to AI agents?
The MCP server exposes Jam's bug reports, recordings, and metadata as standardized tools, so AI agents can query, analyze, and act on bug data without custom integrations.