Compare

Marker.io vs BugTape: use both

Q: Can I run Marker.io and BugTape on the same site?

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

Marker.io collects annotated feedback from clients and QA. BugTape catches errors and failed requests users never report and hands them to your agent.

Short answer: Marker.io is the better tool when a client, a stakeholder or your QA team wants to point at a page and say what is wrong. They click its widget, mark up a screenshot and send it to your issue tracker. 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 now have an MCP server. Use Marker.io 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 Marker.io facts come from Marker.io's pricing page, its help articles on MCP and Jira, and its Website Monitoring page, all read on 26 October 2026.

BugTape does not replace Marker.io. BugTape does not take screenshots, does not let anyone annotate a page, and does not sync with Jira or Linear.

The short version

The question is who starts the report. In Marker.io, a person does. A reporter clicks the widget or the browser extension, marks up a screenshot and sends it. On Team, Business and the Agency plan, the report also carries console logs, network requests and a replay of what the reporter did just before. 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 typo 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

	Marker.io	BugTape
Who starts the report	A person, through a feedback widget on your site or a browser extension. Reporters need no account and no paid seat. (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 and annotations	Yes, on every plan: capture the screen and mark it up with arrows, shapes and text. (pricing)	No. Screenshots and voice notes in the report form are not available yet.
Technical context	Console logs and network requests are captured with every report on Team, Business and the Agency plan. Browser, OS, screen size and URL are attached on every plan. (pricing)	Browser replay rebuilt from DOM events (not video), the failed request, console and stack. Servers have no replay or console. Swift captures handled errors and breadcrumbs only.
Replay	Team, Business and the Agency plan: a replay of what the user did right before reporting. (pricing)	Web reports can include a DOM replay of the lead-up. A bug-button report attaches the last ten minutes of page activity.
Bugs nobody reports	Not listed on its pricing page. Website Monitoring scans chosen pages on a schedule. Accessibility (WCAG) checks are live; Marker.io lists content quality and broken-link checks as coming next. (pricing, Website Monitoring)	Captured automatically when they match a supported failure, with the lead-up.
Repeats	Not stated for feedback reports. Website Monitoring groups the same failing element into one item. (Website Monitoring)	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	Trello, Asana, ClickUp, GitHub, GitLab, Linear, Notion and more on every plan. Jira on Team, Business and the Agency plan. Azure DevOps, Zendesk and Intercom on Business. Two-way Jira sync for status, fields and comments. (pricing, Jira help)	Alerts to Slack, Discord, Telegram, WhatsApp, GitHub issues or your own signed webhook. No Jira or Linear sync.
Agent access	Hosted MCP at `https://connect.marker.io/mcp` with OAuth 2.1 and 33 tools. The agent reads issues, screenshots, console logs and network requests, updates status, priority and assignee, and posts comments. Included on Starter, Team and Business. (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	When an issue is marked done in Jira, Marker.io marks it resolved and emails the reporter. (Jira help)	`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 AI features	AI translation, Magic Rewrite and automatic issue titles on every plan. (pricing)	AI analysis of issues, paid in credits.
Price (checked 26 Oct 2026)	Starter $39 a month billed yearly ($59 monthly): 3 members, up to 10 projects. Team $149 a month billed yearly ($199 monthly): 15 members, up to 50 projects. Business: custom. Agency plan $99 a month billed yearly for eligible agencies. 15-day free trial, no card. No $0 plan is listed. (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 Marker.io widget.
Your client reviews the new pricing page in Marker.io. They mark up a screenshot and say the discount badge overlaps the price. The issue lands in Jira or Linear.
The release ships. 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 Marker.io's MCP and BugTape's MCP to the same client. The agent reads the client's annotated issue from Marker.io 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. When the Jira issue is done, Marker.io emails the client. BugTape watches the next release, and if the checkout failure comes back, the issue reopens as a regression.

Marker.io covers what people show you. BugTape covers what your users hit when nobody is reporting.

When Marker.io is the right tool

A client or stakeholder reviews a website before launch and needs to point at things.
QA or user acceptance testing needs annotated screenshots in Jira, Linear or Trello.
The bug is visual, about copy, or about layout, and no error is thrown.
An agency wants clients to send feedback without accounts or paid seats.

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 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

Marker.io'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 Marker.io alternative?

For bugs nobody reports, yes. For client feedback with annotated screenshots, no. BugTape does not take screenshots or let people mark up a page.

Does Marker.io have an MCP server?

Yes. Marker.io's help center lists a hosted MCP server at https://connect.marker.io/mcp with OAuth sign-in. Its pricing page includes it on Starter, Team and Business (checked 26 October 2026).

Does Marker.io capture errors nobody reports?

Its pricing page does not list automatic capture of errors or failed requests from users who never report. Its scheduled scans check accessibility today. Marker.io lists content quality and broken-link checks as coming next.

Can I run Marker.io and BugTape on the same site?

Yes. Add showButton: false to BugTape's init call so visitors see only the Marker.io 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. Marker.io has two-way Jira sync on Team, Business and the Agency plan.

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.