Cursor

Cursor bug reports over MCP

Hosted BugTape MCP gives Cursor a ranked inbox: DOM replay, the failed request, console and stack. Ack with a PR URL. A human reviews it.

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. The tool list is 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.

The loop inside Cursor

Connect with npx -y bugtape connect cursor, or the mcp.json on the connect page.
subscribe_feed with urgent_critical.
list_recommended_critical. A human's Send to agent, or auto-notify, is waiting under sentToYou even when nothing is listening.
get_repro_context for that bug.
ack_bug with action: "working", then again with prUrl when the pull request is open. The team sees Picked up and PR opened.
A human reviews the pull request.
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.

Paste the AGENTS.md snippet.

Hosted inbox and local-first peers

Approach	What their public pages describe	BugTape
TraceBug	A local `.html` report and a local MCP. Package notes.	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.	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.
BugMojo	Extension or one-click rrweb, repro pack, PR link.	BugTape vs 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 is a checklist that ends at BugTape's hosted MCP. Capture keys cannot open that door.

Start free — no card. Then connect Cursor.

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