# Sentry MCP alternative for agent-fixable bugs

People who search for a Sentry MCP alternative usually want one of two things. One is a thinner wrapper over the same Sentry issues. The other is an agent that can close a production bug: read the evidence, open a pull request, and have a human review it.

This page is the second job. The side-by-side with Sentry as an observability platform is [BugTape and Sentry](/compare/sentry/). Use both is a valid answer. This is not a rip-out guide.

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-10-16.

Public Sentry docs on 2026-10-16 place MCP at https://mcp.sentry.dev/mcp, require OAuth and support optional org/project scoping (`/mcp/{org}/{project}`). Sentry MCP is listed in the official MCP registry as `io.github.getsentry/sentry-mcp`. The Seer issue-fix API describes root cause, generated code changes, and opening a pull request; Seer is a paid add-on and can hand off to Claude Code, Cursor Cloud Agents or GitHub Copilot. BugTape does not claim that loop is unique. BugTape does not claim Sentry lacks regression detection.

## Facts table

| | Sentry MCP | BugTape MCP |
|---|---|---|
| Endpoint | https://mcp.sentry.dev/mcp (org/project scoping) | https://app.bugtape.ai/mcp |
| Auth | OAuth | OAuth 2.1 + PKCE, or `bt_pat_` token; one sign-in |
| Data source | Your Sentry org | BugTape issues (user reports + automatic browser/server failures) |
| Scope | Errors, performance, triage, docs, project management | Ranked inbox, repro pack, ack with a PR URL, subscribe/listen feed, `setup_capture` |
| Wake on new bug | Not claimed here, check Sentry docs | Yes, `listen` on `bugtape://projects/{id}/inbox`, or a signed webhook |
| Cost of agent reads | MCP access is included on the free Developer plan (sentry.io/pricing) | Free and Prepaid credits: 2 credits per bug read; Pro: free |
| Official MCP registry | Yes (`io.github.getsentry/sentry-mcp`) | `ai.bugtape/bugtape` (active) |

## What Sentry MCP does well

Sentry's hosted MCP (`mcp.sentry.dev`) is built for human-in-the-loop coding agents. [Their MCP docs](https://docs.sentry.io/ai/mcp/) and the [Cursor cookbook](https://sentry.io/cookbook/fix-issues-sentry-mcp-cursor/) show agents pulling Sentry context. Seer, a paid add-on, adds root-cause analysis on top of that and can hand off to Claude Code, Cursor Cloud Agents or GitHub Copilot. [Seer's own note](https://blog.sentry.io/seer-mcp-cli-or-coding-agent/) is the right place to read what Seer claims. If that is the workflow you want, keep it.

## What "alternative" should mean

An alternative that only lists the same issues again does not change the loop. BugTape's loop is different on purpose:

1. `list_recommended_critical` is the ranked inbox. Send to agent handoffs are first, under `sentToYou`.
2. `get_repro_context` returns the timeline, the failed request, the console and the stack. It is not a raw DOM dump.
3. `ack_bug` with `working`, then with `prUrl`, so the team sees Picked up and PR opened.
4. A human reviews the pull request.
5. The fix is checked against the next release. A recurrence from a newer release reopens as a regression.

`update_bug`, `merge_bugs`, `delete_bug` and `add_comment` stay human-only. Verified Close refuses the same token that proposed the fix (`E_SELF_VERIFY`). [MCP tools](/docs/mcp-tools/) · [Runner verification](/docs/runner-verification/).

## Other MCP bug tools

One line each, from those vendors' public pages as of 2026-10-16:

| Tool | What their pages describe |
|---|---|
| Sentry MCP + Seer | Hosted MCP inside Sentry; Seer (a paid add-on) does root-cause analysis and can hand off to Claude Code, Cursor Cloud Agents or GitHub Copilot. [Docs](https://docs.sentry.io/ai/mcp/). |
| BugMojo | rrweb evidence, an AGENT assignee, a repro pack and a PR link. [Features](https://www.bugmojo.com/features). [Compared here](/compare/bugmojo/). |
| Ybug | Hosted MCP for a feedback widget. Their docs say MCP is not on the Free plan. [Ybug MCP](https://ybug.io/docs/mcp). |
| Bugfender | Read-only MCP over logs, crashes and devices. Strong mobile logging. BugTape does not match that log depth. [Bugfender MCP](https://bugfender.com/blog/bugfender-mcp/). |
| BugCapture | Local stdio MCP with `list_bugs` and `get_bug` for QA reports. [npm](https://www.npmjs.com/package/bugcapture-mcp). |
| trycatch | Sentry-SDK compatible MCP tool; currently a waitlist / early access. [trycatch.co](https://trycatch.co). |

TraceBug and agenterr are in the same category. BugTape is not the only MCP bug product.

## Feature matrix

Each cell is a BugTape fact from the public docs, or a pointer to that vendor's own page as of 2026-10-16. This table does not copy Sentry's prices. Read those on [Sentry's pricing page](https://sentry.io/pricing/).

| | Sentry | BugTape |
|---|---|---|
| APM, traces, Seer | Sentry's job. Seer (a paid add-on) does root-cause analysis for coding agents and can hand off to Claude Code, Cursor Cloud Agents or GitHub Copilot. [MCP docs](https://docs.sentry.io/ai/mcp/). [Seer note](https://blog.sentry.io/seer-mcp-cli-or-coding-agent/). | BugTape does not do APM, traces, or Seer-style root-cause analysis. |
| Regression after a release | Sentry documents Resolve in next release and a Regressed status. [Issue states](https://docs.sentry.io/product/issues/states-triage/). | A fix you approve is anchored to that report's release. The same failure from a later release reopens as a regression and can alert the team and the agent. |
| Browser evidence | Session Replay for web and mobile (Android, iOS, React Native, Flutter), plus a User Feedback widget and crash-report modal linked to replays. | DOM-event replay, grouping, and a user report button in one inbox. DOM replay is rebuilt from events. It is not a screen video. |
| Agent progress the team sees | Sentry MCP gives the agent production context. [Cursor cookbook](https://sentry.io/cookbook/fix-issues-sentry-mcp-cursor/). | `ack_bug` with `working`, then again with `prUrl`. The team sees Picked up and PR opened. A human reviews the pull request. |
| Free-plan MCP | MCP access is included on the free Developer plan (sentry.io/pricing). | MCP works on Free. Each agent read of a bug's captured events costs 2 credits. Free includes 150 credits a month. On Pro, those reads are free. |
| Where data lives | Check Sentry's regions on their trust pages. | The app runs on Fly.io in Sydney. Postgres is Neon on AWS in ap-southeast-2. Email and payments may be outside Australia. [Trust](/trust/). |
| Drop-in Sentry DSN | A Sentry DSN talks to Sentry. | Not shipped. BugTape does not accept a Sentry DSN. |

Ordinary issue changes (`update_bug`, `merge_bugs`, `delete_bug`, `add_comment`) stay human-only for an agent token. [MCP tools](/docs/mcp-tools/).

## Plan access, only what is published

| Need | Where to look |
|---|---|
| Sentry MCP plan gates | MCP access is included on the free Developer plan (sentry.io/pricing). |
| Ybug MCP | Their docs: read on BASIC, triage on STARTUP and above, not on FREE. |
| BugTape MCP | Every plan, including Free. 2 credits for each agent read of a bug's captured events on Free and Prepaid credits. Free includes 150 credits a month. Pro reads are free. [Pricing](/pricing/). |
| Live `listen` | Pro, or prepaid credits. Otherwise use `list_recommended_critical`. |

## Pick by job

| You need | Use |
|---|---|
| Traces, performance, Seer root-cause | Sentry |
| Mobile remote logs | Bugfender (BugTape does not claim that depth) |
| A feedback widget as the main capture | Ybug or a similar widget. BugTape is not a UAT-widget replacement. |
| An agent that closes production bugs, with a human review and a release check | BugTape |

## FAQ

### Is this a rip-out guide?

No. This is not a rip-out guide. Use both is a valid answer.

### Does BugTape accept a Sentry DSN?

Not shipped. BugTape does not accept a Sentry DSN.

### Can I try the CLI with 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.

## Add BugTape beside Sentry MCP

Keep the Sentry project. Add a BugTape capture key for the app, and a separate agent credential for MCP. There is no drop-in Sentry DSN.

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

Use `connect cursor` for Cursor. Steps: [Connect Cursor](/connect/cursor/) · [Claude Code](/install/claude-code/) · [MCP install](/docs/mcp-install/).

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

## See also

[Sentry alternatives](/alternatives/sentry/) · [Bugsnag vs Sentry (and BugTape)](/compare/bugsnag-vs-sentry/) · [All alternatives](/alternatives/)

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