# BugTape vs DebugBundle

**Short answer:** DebugBundle packages a failure into a structured JSON "debug bundle" (error, request and response, logs, deploy) that your agent fetches over MCP, CLI or API. It has SDKs for server, browser and mobile, GitHub automation, and a free self-hosted option. BugTape is hosted only and centres on real-user browser failures: a DOM replay around each error, failed request or user report, grouped into one issue your agent can read over hosted MCP and acknowledge so your team sees the PR. If you want self-hosting or mobile SDKs today, DebugBundle fits better. If you want browser replay and user reports in the agent's evidence, BugTape does.

No account: `npx -y bugtape --help` prints the commands and does not sign you in. The demo MCP at https://app.bugtape.ai/demo/mcp needs no sign-in. Your own workspace needs one.

Page owner: Jaco Veldsman, hi@bugtape.ai. Last checked 2026-11-02. I build BugTape. Every DebugBundle row below is from [debugbundle.com](https://debugbundle.com/) and its [pricing page](https://debugbundle.com/pricing) on 2 November 2026.

## What DebugBundle publishes

- **Debug bundles.** Versioned, structured JSON per incident: the error, request and response, logs and deploy context. Your agent gets them through MCP, CLI or API, and the dashboard shows the same data.
- **SDKs.** Node, Browser, Python, PHP, Java, .NET, Go, Ruby, Android, iOS, React Native and WordPress.
- **Automation.** Webhooks, GitHub workflows, alerts, health checks, remote probes, product analytics and a local-first mode.
- **Verification fields.** Each bundle carries a `verification` block with `local_verified` and `production_verified`. Its demo says an agent still needs to check application state and verify a fix in a test environment.
- **Pricing.** Free at $0 (750 events a month, 100 bundle requests, 1 member). Solo $4.99 a month adds GitHub automation. Team $19 a month. Self-hosted DebugBundle is free and unlimited.

## What BugTape does

BugTape does not record every visit. The browser SDK keeps a short buffer and sends it with an uncaught error, a failed or hung request, or a user's report. Repeats of the same failure become one issue. DOM replay is rebuilt from events; it is not a screen video. Server SDKs (Node.js, Python) add route, service and release.

Your agent connects once to hosted MCP at `https://app.bugtape.ai/mcp` (OAuth, or a `bt_pat_` token). `list_recommended_critical` is the ranked inbox. `get_repro_context` returns the timeline, failed request, console and stack. `ack_bug` with `working`, then with `prUrl`, shows your team Picked up and PR opened. A human reviews the pull request. When you approve the fix it is anchored to that release, and if real users hit the same failure on a later release BugTape reopens it as a regression.

## Facts

| | DebugBundle (its site, 2026-11-02) | BugTape (our docs) |
|---|---|---|
| Agent access | MCP, CLI and API | Hosted MCP, OAuth or `bt_pat_` |
| Evidence shape | Structured JSON bundle: error, request/response, logs, deploy | Issue with DOM replay, console, network and stack (`get_repro_context`) |
| Browser replay | Not stated on the pages checked | DOM replay around each failure |
| User bug button | Not stated on the pages checked | Yes |
| SDKs | Server, browser, mobile (Android, iOS, React Native) and WordPress | Browser, Node.js, Python; Swift package in alpha with no replay |
| GitHub automation | Yes, from Solo | Your own agent opens the PR; `ack_bug` with `prUrl` shows it to the team |
| Fix check | `local_verified` and `production_verified` fields in the bundle | Fix anchored to the release; a recurrence from real users on a later release reopens as a regression |
| Self-hosting | Yes, free and unlimited | No, hosted only, data in Sydney |
| Free plan | 750 events a month, 100 bundle requests, 1 member | Free, no card, 150 credits a month |
| Paid | Solo $4.99/month, Team $19/month | $10 prepaid = 2,000 credits; Pro $29/month |

## When each fits

Pick DebugBundle when you want to self-host, need mobile SDKs, or want a compact JSON bundle and GitHub workflows for server-side incidents. Pick BugTape when the failures that matter happen in users' browsers, you want the replay and the user's own report in the agent's evidence, and you want your team to see the agent pick the bug up and open the PR. BugTape does not replace Sentry.

## FAQ

### What is a debug bundle?

DebugBundle's name for a structured, versioned JSON file per incident with the error, request and response, logs and deploy context, built for an agent to read.

### Does DebugBundle have an MCP server?

Yes. DebugBundle says your agent can find incidents and fetch bundles through MCP, CLI or API.

### Can I self-host BugTape?

No. BugTape is hosted only, with data in Sydney. DebugBundle offers free, unlimited self-hosting.

### Does BugTape have mobile SDKs?

BugTape has a Swift package in alpha for handled errors and user reports, with no replay. DebugBundle lists Android, iOS and React Native SDKs.

### Can I try BugTape free?

Yes, on the Free plan with no credit card.

## See also

[Compare](/compare/) · [Session replay over MCP](/session-replay-mcp/) · [BugTape vs Rollbar](/compare/rollbar/) · [Self-hosted agent error tracking](/compare/self-hosted-agent-error-tracking/) · [Best error tracking MCP servers](/blog/best-error-tracking-mcp-servers/)

## Try the commands

```bash
npx -y bugtape connect codex   # or claude, cursor
```

Then click Allow once. [Start free](/console/register?utm_source=bugtape_seo&utm_campaign=compare-debugbundle). No card.

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