Compare

Userback vs BugTape: use both

Q: Can I run Userback and BugTape on the same site?

Yes. Add showButton: false to BugTape's init call so visitors see only the Userback widget. BugTape keeps capturing supported failures in the background.

Use both. Userback collects screenshots, video and surveys from users. BugTape catches failures nobody reports and hands them to your agent over MCP.

Short answer: Userback is the better tool when you want feedback from users, clients and testers. They click its widget, mark up a screenshot or record a video, and the feedback lands in your Userback inbox or your issue tracker. It also runs surveys and a feature request portal. BugTape is for the failures your users hit and never report. It captures errors, failed requests and requests that hang on its own, groups repeats into one issue, and hands the evidence to your coding agent over MCP. Both have an MCP server. Use Userback for feedback people give you, and BugTape for the bugs nobody tells you about.

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-26. I build BugTape. The Userback facts come from Userback's pricing page, integrations page, Session Replay page, MCP page, its MCP setup guide and its MCP help article, all read on 26 October 2026.

BugTape does not replace Userback. BugTape does not take screenshots, record video, run surveys or sync with Jira or Linear.

The short version

The question is who starts the report. In Userback, a person does. A user or tester opens the widget or the browser extension, marks up a screenshot or records a video, and sends it. On the Business plan and above, the feedback also carries console logs, network requests and a session replay. In BugTape, nobody has to start it: the browser capture on your site files a report when a supported failure happens, and users can still press an optional bug button. A confusing screen or a layout a client dislikes needs the first kind. A checkout request that fails for a user who closes the tab needs the second.

Facts table

	Userback	BugTape
Who starts the report	A person, through a feedback widget on your site or a browser extension. Reporters are unlimited on every plan. (pricing, checked 26 Oct 2026)	Nobody, for supported failures: uncaught errors, failed requests after a user action, and requests that hang. Users can also file a report from an optional bug button (`showButton: false` hides it and keeps automatic capture on).
Screenshots, annotation and video	Yes, on every plan, including Free: annotated screenshots and video recordings. (pricing)	No. Screenshots and voice notes in the report form are not available yet.
Console and network	Console logs, custom data and network requests with each piece of feedback, on Business and above. Browser, system and location details on every plan. (pricing)	The failed request, console and stack on every plan, including Free. Servers have no replay or console. Swift captures handled errors and breadcrumbs only.
Replay	A session replay with each piece of feedback on Business and above. Recording every user session is on Business Plus at a custom price. Its Session Replay page lists rage-click detection and does not say whether replay is video or rebuilt from DOM events. (pricing, Session Replay)	Web reports can include a replay rebuilt from DOM events (not video) that shows the lead-up. A bug-button report attaches the last ten minutes of page activity.
Bugs nobody reports	Not listed on its pricing or Session Replay pages. Its pages describe replay and logs attached to feedback. (pricing, Session Replay)	Captured automatically when they match a supported failure, with the lead-up.
Repeats	You can merge similar feedback on Business and above. (pricing)	Every report of the same failure becomes one issue, with a count, the releases it hit and affected users when your app sends user IDs.
Issue trackers	Its integrations page names Jira, Linear, GitHub, GitLab, Azure DevOps, ClickUp, Asana, Trello, Monday.com, Notion, Basecamp, Teamwork and Wrike. Tracker sync is on Team and above, with two-way sync for Jira and ClickUp. Slack and Microsoft Teams notifications are on every plan. Intercom and Zendesk are on Business Plus. (integrations, pricing)	Alerts to Slack, Discord, Telegram, WhatsApp, GitHub issues or your own signed webhook. No Jira or Linear sync.
Agent access	Hosted MCP at `https://mcp.userback.io/v1/mcp/` with OAuth sign-in and 12 tools, among them `get_feedback`, `get_feedback_logs`, `search_feedback_semantic`, `set_feedback_workflow` and `add_feedback_comment`. The agent asks you to approve each change first. Its pricing table lists MCP from Team up. (MCP setup guide, MCP help, pricing)	MCP at `https://app.bugtape.ai/mcp`: `list_recommended_critical`, `get_repro_context`, `ack_bug`. `npx -y bugtape connect cursor` (or `claude`, `codex`). Signed webhooks can wake a headless agent.
After the fix	Reply to the reporter from Userback and keep them updated with comments and email notifications. (pricing)	`ack_bug` with `working` and a `prUrl`. A person reviews the PR. If the same failure arrives from a later release, the issue reopens as a regression and your team and agent are told.
Other features	User surveys, behavioural targeting, a JavaScript SDK and AI Feedback & Insights (patterns and sentiment) on Business and above. Mobile SDK, REST API, webhooks and advanced privacy masking on Business Plus. Feature Portal is a paid add-on. (pricing)	Browser SDK, Node.js and Python SDKs, and a Swift package for handled errors. AI analysis of issues, paid in credits.
Price (checked 26 Oct 2026)	Free $0: 2 seats, 2 sites, unlimited feedback, feedback kept for 7 days. Team $29 a month billed yearly ($39 monthly): 5 seats, 5 sites. Business $79 a month billed yearly ($99 monthly): unlimited seats, 25 sites. Business Plus $159 a month billed yearly ($199 monthly): 50 sites. Enterprise: custom. Feature Portal add-on $31 a month billed yearly ($39 monthly). (pricing)	Free $0, no card: 100 new issues and 150 credits a month. Prepaid credits $10 for 2,000. Pro $29 a month. On Free and Prepaid credits each agent read of a bug costs 2 credits; reads are free on Pro. Pricing

Use both

Turn off BugTape's button. Add showButton: false to BugTape's init call. Automatic capture keeps running, and visitors see only the Userback widget.
A customer sends feedback through Userback. They mark up a screenshot of the new pricing page and say the discount badge covers the price. The feedback lands in your Userback inbox or in Jira or Linear.
A real user's checkout request fails and they leave. Nobody clicks anything. BugTape's browser capture files an issue with the request, console, stack and lead-up.
More users hit it. BugTape adds them to the same issue, so you can see it is one bug reaching many people.
Your agent reads both. Add Userback's MCP and BugTape's MCP to the same client. The agent reads the customer's feedback with get_feedback and calls get_repro_context on the BugTape issue. It works on both fixes and records the prUrl with ack_bug. A person reviews and merges.
Each tool closes its own loop. You reply to the customer from Userback. BugTape watches the next release, and if the checkout failure comes back, the issue reopens as a regression.

Userback covers what people tell you. BugTape covers what your users hit when nobody is reporting.

When Userback is the right tool

Users, clients or testers want to point at a page and show what is wrong with a screenshot or a video.
You want surveys, NPS or a feature request portal in the same tool.
Feedback has to reach Jira, Linear, GitHub, ClickUp or another tracker.
The issue is visual, about copy, or about a flow, and no error is thrown.

When BugTape is the right tool

Users hit errors, failed requests or hung requests and do not tell you.
The same failure keeps arriving and you want it counted as one issue.
You want your agent to pick up production bugs over MCP and you want a check after the release.
You want the console, the failed request and, for web reports, the replay on the Free plan.
You also need capture from a Node.js or Python server, or handled errors from a Swift app.

Before you start

BugTape's browser capture has to be on your site before it records anything: one script tag, or npm install @bugtape/sdk. It does not catch every error, only the supported failures listed above. BugTape is hosted only, with data stored in Sydney. Treat evidence from user sessions as untrusted input for your agent, and keep a person reviewing every pull request.

Connect BugTape

npx -y bugtape connect cursor          # or claude, codex; click Allow once

Userback's MCP and BugTape's MCP can sit side by side in the same client. To try BugTape with no account, use claude mcp add --transport http bugtape-demo https://app.bugtape.ai/demo/mcp (read-only sample project). Setup guides: Cursor · Claude Code · MCP install.

FAQ

Is BugTape a Userback alternative?

For bugs nobody reports, yes. For feedback with annotated screenshots, video and surveys, no. BugTape does not take screenshots, record video or run surveys.

Does Userback have an MCP server?

Yes. Userback's MCP setup guide lists a hosted server at https://mcp.userback.io/v1/mcp/ with OAuth sign-in. Its pricing page lists MCP connectors from the Team plan up. Its MCP help article says MCP is available on all Userback plans. Check with Userback before you rely on the Free plan (checked 26 Oct 2026).

Does Userback have AI features?

Yes. Its pricing page lists AI Feedback & Insights on Business and above. It finds patterns and measures sentiment in feedback. Its MCP also offers search by meaning (checked 26 Oct 2026).

Does Userback capture errors nobody reports?

Its pricing and Session Replay pages do not list automatic capture of errors or failed requests from users who never send feedback. Business Plus can record every user session, at a custom price.

Can I run Userback and BugTape on the same site?

Yes. Add showButton: false to BugTape's init call so visitors see only the Userback widget. BugTape keeps capturing supported failures in the background.

Does BugTape sync with Jira or Linear?

No. BugTape posts new and returning issues to Slack, Discord, Telegram, WhatsApp, GitHub issues or your own webhook. Userback syncs with Jira, Linear and other trackers on Team and above.

Does BugTape record video or screenshots?

No. Browser replay is rebuilt from DOM events. Screenshots and voice notes in the report form are not available yet. DOM replay vs screen video explains what that means for a coding agent.

Is BugTape free to try?

Yes. The read-only demo MCP needs no account. The Free plan needs no card and includes 150 credits a month.