Jam.dev MCP honesty matrix — bug-to-fix marketing vs the published tool list
Jam.dev MCP (jam.dev/docs/jam-mcp) pipes recording context — video, console, network, user events — into Claude, Cursor, and friends. Marketing language goes further: the docs lead with "Your agent goes from bug to fix without copy-pasting," the launch blog (jam.dev/blog/meet-the-new-jam-mcp) celebrates "AI agents that ship bug fixes while they sleep," and a docs example says Jam MCP + Claude Code can "ship a ready-to-review PR."
The same docs page lists Available MCP tools — and they are Jam context readers plus Jam workspace CRUD: getDetails, getConsoleLogs, getNetworkRequests, getUserEvents, analyzeVideo, createComment, updateJam, listJams, recording-link helpers, and related aliases. There is no create_pr, open_pr, codebase, or git write tool. Feedback DevTools is honest about a different surface: create_github_issue / create_tracker_issue plus source-mapped local-agent context with file:line. We do not claim server-side auto-opened or auto-merged PRs.
Feedback DevTools is our product. Jam MCP marketing and Available MCP tools sourced from jam.dev/docs/jam-mcp and jam.dev/blog/meet-the-new-jam-mcp; pricing from jam.dev/pricing — lastChecked September 22, 2026 ~7pm Asia/Jerusalem. Please verify before purchase.
Feedback DevTools vs Jam.dev MCP
| Feedback DevTools | Jam.dev MCP | |
|---|---|---|
| Marketing claim: bug to fix / ship bug fixes / ready-to-review PR | No — FDT does not claim MCP ships fixes or opens PRs; local agent writes code from file:line context | Yes — docs: "agent goes from bug to fix"; blog: "AI agents that ship bug fixes while they sleep"; docs example: "ship a ready-to-review PR" |
| Published MCP tools (open-PR honesty) | get_feedback_context, list_open_feedback, list_clusters, create_github_issue, create_tracker_issue, mark_feedback_resolved… | getDetails · getConsoleLogs · getNetworkRequests · getUserEvents · analyzeVideo · createComment · updateJam · listJams (+ screenshots/video/frames, folders, recording links, fetch/search aliases) — context + Jam workspace CRUD; no create_pr / open_pr / codebase / git write |
| MCP tools that open GitHub / Linear tickets | Yes — create_github_issue (#57) + create_tracker_issue Linear (#59) with component + file:line in the body | No dedicated tracker-create / create_pr tools in the published list — docs example pairs Jam MCP with Linear MCP for tickets |
| Open GitHub PR from MCP tool | No — create_github_issue + local-agent fix path (Cursor/Claude opens a PR if you ask; not a Jam-style MCP PR tool) | No dedicated create_pr / open_pr / git write tool — PR would be the coding agent using Jam context |
| Auto-open / auto-merge PRs server-side | No — we do not claim server-side auto-opened or auto-merged PRs | No — marketing implies sleeping agents / ready-to-review PRs; published Jam MCP tools do not open or merge GitHub PRs |
| Source map on capture (component + file:line) | Yes — pinned at collect time for the local agent | Video, console, network, user events, metadata — rich repro context, not React component file:line |
| Who applies the code fix | Your local Cursor / Claude agent (from MCP context or Claude Code prompt) | Your AI coding agent (Cursor, Claude Code, etc.) using Jam recording context — not a Jam-server PR opener |
| Post comments from MCP | Via tracker ticket body / local agent workflow | Yes — createComment / editComment / addReaction |
| List / search recordings from MCP | list_open_feedback / list_clusters | Yes — listJams (+ fetch/search aliases) |
| Free plan | Yes — unlimited feedback, forever | Yes — Free: 30 Jams, MCP debug included |
| Paid entry price | $9/mo per project (Pro) | Team from $14/creator/mo (yearly) |
Jam MCP marketing quotes + Available MCP tools verified on jam.dev/docs/jam-mcp and jam.dev/blog/meet-the-new-jam-mcp; pricing on jam.dev/pricing — lastChecked September 22, 2026 ~7pm Asia/Jerusalem
Where Jam.dev MCP is genuinely strong
Credit where due — Jam MCP is a real debugging unlock if:
- You already record bugs as Jam videos and want Claude/Cursor to pull console, network, user events, and video analysis without copy-paste.
- Your team lives in Jam folders + recording links and wants agents to listJams, updateJam, createComment, and manage recording links from the IDE.
- Rich repro context (video chapters, frames, transcripts) matters more than React component file:line source maps.
- You want MCP on the Free plan for small teams (30 Jams) before paying per creator.
Where Feedback DevTools is different (honest foil)
- Marketing vs tools. Jam docs/blog say "bug to fix," "ship bug fixes while they sleep," and "ready-to-review PR"; the published Available MCP tools are Jam context + workspace CRUD — no create_pr / open_pr / codebase / git write (lastChecked September 22, 2026 ~7pm Asia/Jerusalem). We quote both so buyers are not surprised.
- Tickets with file:line. create_github_issue and create_tracker_issue open GitHub/Linear tickets whose bodies carry component + file:line from capture. Jam's published list has no create_github_issue / create_pr equivalent.
- Local-agent path, not server-side PRs. Your Cursor/Claude agent applies the fix from FDT context. We do not claim to auto-open or auto-merge PRs on a server-side clone (contrast Usero request_ai_pr on /compare/usero-alternative). Distinct from Marker#68, BugHerd#67, Usero#66.
- Capture-time source maps. Every item pins the React component and file path:line so the agent starts from a known path instead of rediscovering from a video + console dump alone.
- Pricing shape. Unlimited free collection; Pro is $9/mo per project. Jam Free caps at 30 Jams; Team starts at $14/creator/mo.
Pricing, side by side (as of September 22, 2026)
- Feedback DevTools: Free plan ($0, unlimited feedback) · Pro $9/mo per project
- Jam.dev: Free ($0, 30 Jams, MCP included) · Team from $14/creator/mo billed yearly · Enterprise custom (sources: jam.dev/pricing; MCP docs: jam.dev/docs/jam-mcp; blog: jam.dev/blog/meet-the-new-jam-mcp)
MCP honesty is about capability claims, not sticker shock — but one FDT Pro project is $9/mo vs Jam Team at $14/creator/mo once you outgrow the 30-Jam Free cap.
Who should choose what
- Choose Jam.dev MCP if your bug archive is Jam recordings and you want agents to load video/console/network context (and manage Jam comments/folders/links) without leaving the IDE.
- Choose Feedback DevTools if you want visual feedback with file:line on capture, MCP tools that create GitHub/Linear tickets, and a local-agent fix path — without reading "bug to fix" / "ship while they sleep" marketing as a published create_pr tool.
- Neither MCP is a silent auto-merge bot; both expect a human review step. The honest foil is what the published tools actually do. Distinct from Marker open-PR marketing, BugHerd codebase/CMS/design marketing, and Usero request_ai_pr.
Frequently asked questions
What does Jam.dev MCP marketing claim?
Per jam.dev/docs/jam-mcp and jam.dev/blog/meet-the-new-jam-mcp (lastChecked September 22, 2026 ~7pm Asia/Jerusalem): the docs lead with "Your agent goes from bug to fix without copy-pasting"; the blog celebrates "AI agents that ship bug fixes while they sleep"; a docs implementation-planning example says Jam MCP + Claude Code can "ship a ready-to-review PR."
What tools does Jam MCP actually publish?
The Available MCP tools table on jam.dev/docs/jam-mcp lists context readers and Jam workspace CRUD: getDetails, getConsoleLogs, getNetworkRequests, getUserEvents, analyzeVideo, getScreenshots/getFrames/video helpers, listJams, createComment/updateJam/folder + recording-link management, and fetch/search aliases. Those load and organize Jam data — they are not create_pr, open_pr, codebase, or git write tools.
Does Jam MCP open pull requests?
Marketing language implies agents that fix bugs and ship ready-to-review PRs, but the published tool list has no create_pr / open_pr / GitHub write tool (lastChecked September 22, 2026 ~7pm Asia/Jerusalem). A PR, if any, is the coding agent's git workflow using Jam context — not a Jam MCP PR tool.
Does Feedback DevTools auto-open or auto-merge GitHub PRs server-side?
No. Feedback DevTools MCP creates tracker tickets (create_github_issue, create_tracker_issue for Linear) and supplies source-mapped context / Claude Code prompts so your local agent can write the fix. We do not claim to auto-open or auto-merge pull requests server-side.
How does Feedback DevTools MCP foil Jam MCP?
FDT is honest about a different surface: capture-time component + file:line, create_github_issue / create_tracker_issue, and a local-agent path. Jam MCP is strong at piping recording context into the agent. Marketing that implies sleeping ship-bots or MCP-opened PRs should be read against the Available MCP tools table on jam.dev/docs/jam-mcp.
Collect source-mapped feedback and open GitHub/Linear tickets from MCP — free.