All five tools let an agent read feedback over MCP. Marker.io exposes the richest report data (console and network logs) but keeps the agent read-only. Jam is a one-way link handoff. BugHerd allows task triage in beta. MarkLayer is the only one with a live two-way loop: the agent watches a room, marks annotations in progress, resolves them, and replies, with every status change visible to the humans watching.
As of August 2026, verified against each vendor's published documentation:
| Tool | Agent can read | Agent can act | Price floor |
|---|---|---|---|
| MarkLayer | Annotations with CSS selector, text fingerprint, computed styles, detected React/Vue/Svelte component, thread history | Watch live, acknowledge, resolve, dismiss, reply | Free |
| Marker.io | Reports with screenshots, console logs, network requests, browser/OS | Read and draft only; cannot resolve or reply | $59/mo ($39 annual) |
| BugHerd | Task details with screenshots, CSS selectors, browser/OS, severity | List, create, update tasks (beta) | $50/mo (5 members) |
| Jam.dev | A pasted Jam link: console, network, user actions, video transcript | Nothing; one-way handoff | Free tier |
| Usersnap | Collected feedback via hosted MCP (OAuth) | Query feedback, create opportunities | ~€39/mo |
Two design decisions separate the field.
Read-only vs two-way. Marker.io documents that its agent integration deliberately stops short of resolving or replying: a human stays in the loop by policy. Jam's model is a link you paste, after which the agent works alone. MarkLayer inverts this: the agent is a participant in the room, and the human oversight happens live, on the annotations themselves, as statuses flip from open to in progress to resolved.
Report context vs element context. Marker.io and Jam attach runtime evidence: console errors, network traces. MarkLayer attaches code-location evidence: the selector, the computed styles, and the framework component behind the annotated element, which is what an agent needs to find the file to edit. BugHerd sits between, with selectors but no logs. If your bugs are mostly "this JavaScript is failing", runtime logs win. If they are mostly "this element is wrong", element context wins.
Every tool here uses a one-line install. MarkLayer's, for Claude Code:
claude mcp add marklayer -- npx -y marklayer-mcp --room <room-id>Cursor, Codex, Windsurf, and other MCP clients take the same npx -y marklayer-mcp command in their MCP configuration. The server is published on npm as marklayer-mcp, and each MarkLayer share page shows the command with the room id filled in.
Match the tool to the failure mode you report most. Runtime bugs with logs: Marker.io (paid) or Jam (free tier). Task-tracked QA with triage: BugHerd. Feedback-program queries: Usersnap. Visual and UI feedback that an agent should fix while reviewers watch: MarkLayer, and it is the only free option of the five.
MarkLayer is free, requires no sign-up, and works on any webpage. Recipients of your share links don't need to install anything.
Add to Chrome