# Cursor bug reports over MCP

The job is to stop pasting stack traces into Cursor. BugTape already holds the production issue: what the user did, the failed request, the console, the stack, who hit it, and which release. Cursor reads that over hosted MCP and can open a pull request. A human reviews the pull request.

This is production capture plus an optional user report button, then an agent handoff. It is not only a QA click-capture. The install steps live on [Connect Cursor](/connect/cursor/). The tool list is [MCP tools](/docs/mcp-tools/).

## What the agent actually receives

`get_repro_context` returns a compact pack: timeline, failed request, console and stack. It is not a raw rrweb dump, and it is not a screen video. DOM replay is rebuilt from DOM events in the browser SDK. Server reports do not include that replay.

Privacy modes are Standard, Strict (page text becomes blocks, query strings stripped, bodies dropped), Errors only (`disableDomRecording: true`), and sealed client details. [Trust](/trust/).

## The loop inside Cursor

1. Connect with `npx -y bugtape connect cursor`, or the mcp.json on the [connect page](/connect/cursor/).
2. `subscribe_feed` with `urgent_critical`.
3. `list_recommended_critical`. A human's Send to agent, or auto-notify, is waiting under `sentToYou` even when nothing is listening.
4. `get_repro_context` for that bug.
5. `ack_bug` with `action: "working"`, then again with `prUrl` when the pull request is open. The team sees Picked up and PR opened.
6. A human reviews the pull request.
7. Approve the fix against the release. A later release that hits the same failure reopens it.

`listen` wakes the agent on Pro or when the workspace holds prepaid credits. On Free, the ranked list is the start. Each agent read of captured events on Free or Prepaid credits costs 2 credits. Free includes 150 credits a month. Pro reads are free. [Pricing](/pricing/).

Paste the [AGENTS.md snippet](/docs/examples/AGENTS.md).

## Hosted inbox and local-first peers

| Approach | What their public pages describe | BugTape |
|---|---|---|
| TraceBug | A local `.html` report and a local MCP. [Package notes](https://npm.io/package/tracebug-sdk). | Hosted MCP at `https://app.bugtape.ai/mcp`, plus capture that runs in production. |
| BugCapture | Local stdio, `list_bugs` / `get_bug`, aimed at QA repro packs. [npm](https://www.npmjs.com/package/bugcapture-mcp). | Automatic uncaught errors, failed requests and hung requests, grouped, with releases and users when you send ids. |
| Speedydebug | Dev-time debugging (see their site). | Production issues that are already grouped before the agent opens. |
| Sentry MCP | Observability context and a Cursor cookbook. | Complementary. [BugTape vs Sentry](/vs/sentry/). |
| BugMojo | Extension or one-click rrweb, repro pack, PR link. | [BugTape vs BugMojo](/compare/bugmojo/). |

BugTape is not the only Cursor MCP bug tool. It is not a replacement for a UAT widget.

## If the socket fails

[Cursor MCP connection failed](/guides/cursor-mcp-connection-failed/) is a checklist that ends at BugTape's hosted MCP. Capture keys cannot open that door.

[Start free](/console/register?utm_source=bugtape_seo&utm_campaign=cursor-bug-reports) — no card. Then [connect Cursor](/connect/cursor/).

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