Compare
Sentry MCP alternative for agent-fixable bugs
Sentry MCP gives agents production context. BugTape adds a ranked inbox, repro evidence, ack with a PR URL, and a regression wake-up. A human reviews it.
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 vs Sentry. Use both is a valid answer. This is not a rip-out guide.
What Sentry MCP does well
Sentry's hosted MCP (mcp.sentry.dev) is built for human-in-the-loop coding agents. Their MCP docs and the Cursor cookbook show agents pulling Sentry context. Seer adds root-cause analysis on top of that. Seer's own note 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:
list_recommended_criticalis the ranked inbox. Send to agent handoffs are first, undersentToYou.get_repro_contextreturns the timeline, the failed request, the console and the stack. It is not a raw DOM dump.ack_bugwithworking, then withprUrl, so the team sees Picked up and PR opened.- A human reviews the pull request.
- 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 · Runner verification.
The MCP bug-tool landscape
One line each, from those vendors' public pages as of 2026-10-07:
| Tool | What their pages describe |
|---|---|
| Sentry MCP + Seer | Hosted MCP and root-cause analysis inside Sentry. Docs. |
| BugMojo | rrweb evidence, an AGENT assignee, a repro pack and a PR link. Features. Compared here. |
| Ybug | Hosted MCP for a feedback widget. Their docs say MCP is not on the Free plan. Ybug MCP. |
| Bugfender | Read-only MCP over logs, crashes and devices. Strong mobile logging. BugTape does not match that log depth. Bugfender MCP. |
| BugCapture | Local stdio MCP with list_bugs and get_bug for QA reports. npm. |
trycatch, 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-07. This table does not copy Sentry's prices. Read those on Sentry's pricing page.
| Sentry | BugTape | |
|---|---|---|
| APM, traces, Seer | Sentry's job. Seer does root-cause analysis for coding agents. MCP docs. Seer note. | 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. | 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 | Sentry documents its own replay product. | 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. | 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 | Check Sentry's current plan. This page does not state their price. | 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. |
| 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.
Plan access, only what is published
| Need | Where to look |
|---|---|
| Sentry MCP plan gates | Sentry's own pricing and MCP docs. Not repeated here. |
| 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. |
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 |
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.
npx -y bugtape connect claudeUse connect cursor for Cursor. Steps: Connect Cursor · Claude Code · MCP install.
Start free — no card.
Your team reviews the PR. Agents do not silent-ship.