# BugTape vs BugMojo

BugMojo and BugTape both give a coding agent repro evidence over MCP, and both can point at a pull request. This page is a matrix of published differences. It does not rank the products, and it does not call BugTape the only MCP bug product.

BugMojo's own pages (as of 2026-10-07) describe rrweb replay, console, network and screenshot capture from a browser extension, an AGENT assignee, `get_repro_pack`, `link_pr`, agents that can push a PR, and QA verification (plus regression suites promoted from fixed issues). Read that on [bugmojo.com](https://www.bugmojo.com/) and [their features page](https://www.bugmojo.com/features). They do publish PR linking. This page does not say otherwise.

## Matrix

| | BugMojo (their pages) | BugTape (our docs) |
|---|---|---|
| How a bug is filed | Extension or one-click capture, aimed at a QA workflow. | Automatic capture of uncaught errors, failed requests and hung requests. User report button is optional. Browser, Node.js, Python and Streamlit can share one project. [Python](/docs/python/). |
| Grouping | See their features page. | One issue per failure, with a count, releases, and affected users when ids are sent. |
| Agent progress | AGENT assignee, repro pack, PR link; agents can push a PR; QA verifies (their pages). | `ack_bug` with `working` and `prUrl`. The team sees Picked up and PR opened. A human reviews the pull request. |
| After the release | Their pages describe QA verification and regression suites that learn from fixed bugs. Read their docs for the exact rule. | The approved fix anchors to the report's release. The same failure from a later release reopens as a regression. |
| Who may verify | QA verifies, on their description. | Verified Close needs a different token from the fixer (`E_SELF_VERIFY`). Runner enrollment is a human admin step. [MCP tools](/docs/mcp-tools/). |
| MCP on Free | Check BugMojo's current plan page. Not stated here. | MCP on every plan. Free and Prepaid credits: 2 credits for each agent read of captured events. Free includes 150 credits a month. Pro reads are free. `listen` needs Pro or prepaid credits. [Pricing](/pricing/). |
| Where data lives | Check BugMojo. | Fly.io Sydney, Neon Postgres in ap-southeast-2. Email and payments may be outside Australia. No SOC 2 report yet. [Trust](/trust/). |

DOM replay in BugTape is rebuilt from DOM events. It is not a screen video. Fatal iOS crash capture is not available. BugTape does not claim Bugfender's mobile log depth, and it is not a UAT-widget replacement.

## When BugMojo fits

Choose BugMojo when the workflow is QA-led and the bug is filed from the browser extension on purpose. Their verification model is QA-led (and regression suites on their pages). Use their docs for that.

## When BugTape fits

Choose BugTape when production should file the issue without a click, including server and Streamlit errors, and you want Send to agent, a PR URL on the issue, and a release check. You can read both products' MCP docs and run the one that matches the job.

## Connect BugTape

```bash
npx -y bugtape connect claude
```

`connect cursor` is the Cursor form. [Claude Code](/install/claude-code/) · [Cursor](/connect/cursor/) · [MCP install](/docs/mcp-install/). Sentry can stay in place: [BugTape vs Sentry](/vs/sentry/).

[Start free](/console/register?utm_source=bugtape_seo&utm_campaign=compare-bugmojo) — no card.

Your team reviews the PR. Agents do not silent-ship.