Skip to content
MCP server

BugTape demo

Hands browser bug evidence to Claude Code, Cursor or Codex over MCP; read-only demo

Answered our latest tool-list check 3 hours ago with 14 tools. It will be marked verified after 3 successful checks in 7 days.

Install
Pricing
Free
Platforms
API, Web
Runs
Remotely
Version
1.0.0
Listing updated
today

Similar MCP servers

About BugTape demo

BugTape demo is a free MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.

The README and registry entry describe this as a read-only sample shop with captured bug evidence, reachable over streamable HTTP with no sign-in or key. It is a way to see what an agent receives from BugTape before connecting a real workspace. The demo returns a captured issue, including the steps the user took, the failed request, console output and stack trace.

The demo is the no-account entry point to BugTape's MCP tools. An agent can list ranked issues, pull the reproduction context for one report and acknowledge work on it. The sample data is synthetic and the site notes that an agent's replies will differ from its illustrations.

It suits developers who want to test an MCP workflow for bug triage before giving a coding agent access to their own app's reports.

Install

Run in a terminal

claude mcp add --transport http bugtape-demo https://app.bugtape.ai/demo/mcp

Add to Settings → Connectors → Add custom connector

https://app.bugtape.ai/demo/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "bugtape-demo": {
      "url": "https://app.bugtape.ai/demo/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "bugtape-demo": {
      "type": "http",
      "url": "https://app.bugtape.ai/demo/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "bugtape-demo": {
      "serverUrl": "https://app.bugtape.ai/demo/mcp"
    }
  }
}

Add to Grok Bot desktop app → Connect apps → Add a custom connector

https://app.bugtape.ai/demo/mcp

Enter a Name (for example "BugTape demo"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin.

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "bugtape-demo": {
      "type": "http",
      "url": "https://app.bugtape.ai/demo/mcp"
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Tools this server provides (14)

Read directly from the server.

All 14 tools say they're read-only.

From the server's own tool annotations; not verified by us.

list_bugsSays read-only
List bugs for the organization (flat, one row per deduplicated report). Supports filtering by status, severity, project, platform, deliveryFeed (all | urgent_critical | ui_ux), and text search. Each row includes affected_user_count, repeat_user_count, and user_spread (user_specific vs widespread). Diagnostic-class signals are excluded by default. Prefer list_bug_groups for grouped triage. A new pr
get_bugSays read-only
Get full details of a bug including title, description, severity, status, reporters, AI summary, environment info, report count, affected_user_count, repeat_user_count, and user_spread (user_specific vs widespread). Use get_bug_users for the per-user roster. isExample: true marks BugTape's practice bug (see exampleNote).
get_bug_eventsSays read-only
Get session events for a bug (DOM, network, console, clicks, errors). Prefer passing occurrenceId so events are not mixed across captures.
get_repro_contextSays read-only
Build an agent-consumable reproduction pack: evidence (timeline, status, env) separate from inference (AI summary). Prefer occurrenceId so sessions are not interleaved. Not raw rrweb. Same pack as resources/read bugtape://bugs/{bugId}/repro. For an example bug (isExample: true) the pack is practice data and costs no credits.
list_projectsSays read-only
List all projects in the organization with their bug counts.
get_project_statsSays read-only
Get aggregate statistics for a project (server-computed over bugs in the elected delivery feed, not a sample): counts by status and severity, daily timeline, top unresolved bugs by report count, MTTR, health score, and previous-period comparison.
get_bug_occurrencesSays read-only
List the individual occurrences grouped under a bug. Use this to see which users, sessions, releases, or environments were affected.
get_bug_usersSays read-only
Who hit this bug: one row per affected end user (the app's identify() userId, else reporter email, else an anonymous IP-hash key) with firstSeen, lastSeen, occurrenceCount, platforms (web/ios/…), lastRelease and lastOccurrenceId. Pass a row's userKey to get_user_timeline to see everything that user experienced across bugs, or to get_repro_context via occurrenceId=lastOccurrenceId.
get_live_occurrencesSays read-only
Get the most recent occurrences across the organization. Useful for live monitoring and tester workflows. Honors deliveryFeed (tool arg, else PAT / project).
get_current_orgSays read-only
Return the credential workspace. Agent PATs resolve only their own workspace; human sessions use BUGTAPE_ORG_ID.
get_bug_historySays read-only
Get the full audit trail of status/severity changes and assignments on a bug, including who changed what and when.
get_similar_bugsSays read-only
Find other bugs similar to the given bug, ranked by similarity score (0-100, fingerprint + title overlap). Returns up to 5 matches. Useful before merging or triaging.
list_bug_groupsSays read-only
Grouped triage view: bugs collapsed across pages by error signature (one group per distinct error within a project, even when dedup created many bug rows). Each group includes projectId + groupKey (the stable group identity), a representative sampleBugId/sampleTitle, instanceCount, occurrenceCount, sessionCount, userCount, maxSeverity, topStatus, signalReason (why the classifier flagged it), brows
list_recommended_criticalSays read-only
Start here. Returns `sentToYou` first: bugs a person sent you with "Send to agent" (fix these first), then the prefiltered agent inbox: one row per signature group, new unique issues scored critical/high (or regressions). `id` is the best qualifying member. `member_id_sample` is at most 8 member ids; `instance_count` is the full count and `instances_path` lists the rest. Use this instead of list_b

What it does

Read-only sample data
The demo serves captured bug evidence from a sample shop without requiring an account or API key.
Streamable HTTP endpoint
Connects to a remote MCP endpoint over streamable HTTP, so no local package install is needed.
Reproduction context
Returns what the user did, the failed request, console output and stack trace for a single report.
Ranked issue list
Exposes a recommended-critical list that orders open issues for fixing.

Good for

  • Evaluate how an agent would triage bugs before connecting a real workspace
  • Walk through one captured bug end to end with an MCP client
  • Test MCP client configuration against a remote server without sign-in

Pricing

Free

Demo is free and needs no sign-in; full workspace has Free, prepaid credits and Pro plans.

Prices change. Check bugtape.ai before you buy.

BugTape demo FAQ

Does the demo need an account or key?

No. The demo MCP at https://app.bugtape.ai/demo/mcp is read-only and needs no sign-in.

What does the demo contain?

According to the site, it is a read-only sample shop with real evidence. The page also describes its illustrations as synthetic data.

Can the demo fix or change anything?

No. The demo is read-only.

Is BugTape demo free?

Yes. BugTape demo is free to use.

How do I add BugTape demo to Claude Code?

Run this command in your terminal: claude mcp add --transport http bugtape-demo https://app.bugtape.ai/demo/mcp

What are the best alternatives to BugTape demo?

The closest alternatives to BugTape demo are BugTape, Tracebug, Midge, BugMojo and BugBoard.

Where this comes from

  • Description: written from the project's website and its MCP Registry entry.
  • Status and tools: checked automatically by AIPoweredBot on 19 November 2026.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers