Compare

Gleap vs BugTape: use both

Q: Does Gleap have an MCP server?

Yes. Gleap hosts one at https://mcp.gleap.io/mcp with over 90 tools for tickets, contacts, help center, feature requests, statistics and coding sessions. It is included from the Team plan. Starter has no API or MCP access.

Gleap is a support platform: bug reports, chat, AI bot, surveys and Kai Code PRs. BugTape catches failures users never report and hands them to your agent.

Short answer: Gleap is a customer support platform for software teams. It puts in-app bug reports, live chat, an AI support bot, surveys, feature requests and a help center in one inbox, and its Kai Code agent can open a pull request from a ticket. A Gleap bug report starts when a person opens the report form, or when your code calls Gleap for a specific exception. BugTape catches the failures your users hit and never report. It files uncaught errors, failed requests and requests that hang with no form and no per-error code, groups repeats into one issue, and hands the evidence to your coding agent over MCP. Pick Gleap when you want support and feedback in one tool. Add BugTape when you want the bugs nobody reports.

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 Gleap facts come from Gleap's pricing page, its pages on in-app bug reporting, session replay, Kai Code and the Gleap MCP server, all read on 26 October 2026.

This page is not a ranking. Gleap does many jobs that BugTape does not do: support chat, an AI support bot, surveys, feature requests, a help center and product tours.

The short version

The two tools start from different places. Gleap starts from the customer. A customer or tester opens the widget, marks the bug on a screenshot and sends it, and the SDK attaches the replay, console and network logs and device data. Your team answers that person in the same ticket. BugTape starts from the failure. The browser capture on your site files a report when a supported failure happens, even if the user closes the tab and says nothing. Users can still press an optional bug button. If your users write in when something breaks, Gleap gives you the conversation and the fix in one place. If they leave without a word, BugTape is the one that sees it.

Facts table

	Gleap	BugTape
What it is	A customer support platform: in-app bug reports, shared inbox, live chat, AI support bot (Kai Support), surveys, feature requests, help center, release notes and product tours. Gleap (checked 26 Oct 2026)	A bug capture tool for teams that hand bugs to coding agents. It records failures, groups them, and serves the evidence over MCP. No chat, surveys or help center.
Who starts a report	A person, from the widget form or by shaking a phone. Your code can also call `Gleap.sendSilentCrashReport` for a caught exception or failed request; by default that report has logs and metadata and leaves out the replay. Gleap (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).
Evidence in a web report	Marked screenshot, optional screen recording of up to two minutes with voice, console logs (up to 500 entries), the last 30 network requests, device data and custom data. Web session replay is built from page changes, is in beta, is included from Team, and is off until you turn it on. Gleap (checked 26 Oct 2026)	Browser replay rebuilt from DOM events (not video), the failed request, console and stack. A bug-button report attaches the last ten minutes of page activity. Screenshots and voice notes in the report form are not available yet.
Platforms	JavaScript SDK for the web. Native iOS and Android SDKs with shake to report and a screenshot-based app replay. React Native, Flutter and Capacitor wrappers. Gleap (checked 26 Oct 2026)	Browser SDK with replay. Node.js and Python server SDKs, with no replay or console. Swift captures handled errors and breadcrumbs only. No Android SDK.
Repeats	Each report is a ticket on a bug board. Kai Resolve can look up similar tickets during an investigation. Gleap (checked 26 Oct 2026)	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. A repeat report costs 0 credits.
Agent access	Hosted MCP at `https://mcp.gleap.io/mcp` (US projects use `https://mcp.us.gleap.ai/mcp`) with OAuth, or API key headers. Gleap lists over 90 tools across tickets, contacts, help center, outbound messages, feature requests, statistics, workflows and coding sessions. Claude Code, Codex and Cursor are named. Team plan and up. Gleap MCP (checked 26 Oct 2026)	Hosted MCP at `https://app.bugtape.ai/mcp` with OAuth: `list_recommended_critical`, `get_repro_context`, `ack_bug`. `npx -y bugtape connect cursor` (or `claude`, `codex`). On every plan. A read-only demo MCP needs no account.
Who writes the fix	Kai Code plans the change, edits the code, runs the tests and opens a pull request linked to the ticket. It runs hosted by Gleap, on your machine, or inside your own Claude Code, Codex or Cursor, which report progress back to the ticket. Your engineers review and merge. Kai Code (checked 26 Oct 2026)	Your own coding agent. BugTape supplies the evidence and does not write code. The agent records `working` and a `prUrl` with `ack_bug`. A person reviews the PR.
After the fix	A teammate confirms the merged fix is live, then Gleap sends the customer an update in the same conversation. Kai Code (checked 26 Oct 2026)	If the same failure arrives from a later release, the issue reopens as a regression and your team and agent are told.
Privacy and hosting	Password inputs are masked in replay by default; you can mask all inputs and exclude endpoints and headers from network logs. EU or US data residency, chosen at signup. Gleap (checked 26 Oct 2026)	Form fields are masked in the browser. `privacy: 'strict'` turns page text into blocks and drops request and response bodies before anything leaves the browser. Data is stored in Sydney. Hosted only. Trust
Price	No free plan. Every plan has a 7-day trial that needs a card. Starter $29 a month billed yearly ($35 monthly): one seat, one project, bug reports, live chat and the AI bot, with no session replay and no API or MCP. Team $149 a month billed yearly ($179 monthly): unlimited seats, session replay, MCP, Kai Resolve and Kai Code. Pro $299 a month billed yearly. AI usage is billed separately. Gleap pricing (checked 26 Oct 2026)	Free $0, no card: 100 new issues and 150 credits a month, with MCP. 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

A customer writes in through the Gleap widget. They mark the broken button on a screenshot. Your support team answers them in Gleap, and Kai Code or your engineer works the ticket.
Another user hits a failed checkout request and leaves. Nobody opens a form. BugTape's browser capture files an issue with the request, console and lead-up.
More users hit it. BugTape adds them to the same issue instead of opening new ones, so you can see one bug reaching many people.
Your agent picks it up. It calls get_repro_context, works on the fix, and records the prUrl with ack_bug. A person reviews and merges.
BugTape watches the next release. If the same failure comes back, the issue reopens as a regression.

Gleap's MCP and BugTape's MCP can sit side by side in the same Claude Code, Codex or Cursor setup.

When Gleap is the right tool

You want bug reports, live chat, an AI support bot, surveys and feature requests in one workspace.
Your support team needs to answer the person who reported the bug, in the same ticket.
Customers should mark the bug on a screenshot or record their screen with voice.
You ship native iOS and Android apps, or React Native, Flutter or Capacitor apps.
You want an agent that opens the pull request for you, from the ticket.
You need your data in the EU or the US.

When BugTape is the right tool

Users hit errors, failed requests or hung requests and don't tell you.
The same failure keeps arriving and you want it counted as one issue.
You already use Claude Code, Cursor or Codex and want it to read production bugs over MCP, on a free plan.
You want a check after the release that reopens the issue if the failure comes back.
You want Node.js or Python server errors next to browser failures.

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 doesn't catch every error, only the supported failures listed above. BugTape is hosted only. 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

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 Gleap alternative?

For catching failures and handing them to a coding agent, yes. For customer support, live chat, surveys, feature requests or a help center, no. BugTape does none of those.

Does Gleap report errors automatically?

Gleap attaches the replay, logs and device data automatically once a person sends a report. A report without a person needs a Gleap.sendSilentCrashReport call in your code, and by default that report leaves out the replay. BugTape files uncaught errors, failed requests and hung requests without a form or a call.

Does Gleap have an MCP server?

Yes. Gleap hosts one at https://mcp.gleap.io/mcp with over 90 tools for tickets, contacts, help center, feature requests, statistics and coding sessions. It is included from the Team plan. Starter has no API or MCP access.

Can Gleap write the fix?

Yes. On Team and up, Kai Code plans the change, runs the tests and opens a pull request linked to the ticket. Your engineers review and merge. BugTape does not write code; your own agent does.

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. Gleap's web replay is also rebuilt from page changes, and Gleap adds a marked screenshot and an optional screen recording. DOM replay vs screen video explains the difference 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 MCP and 150 credits a month. Gleap has no free plan and offers a 7-day trial with a card.