BugTape demo

ai.bugtapePublished by bugtape.aiOfficial publisherv1.0.0Updated Oct 27, 2026

Read-only sample shop with captured bug evidence. No account or key needed.

The publisher's own server: BugTape

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Read-only BugTape demo workspace that lets an assistant browse sample bug reports with captured session evidence and build reproduction packs.

What you can do
  • List and read bugs, with filters by status, severity, project, platform and delivery feed
  • Inspect session evidence for a bug: DOM, network, console, clicks and errors, plus a reproduction pack separating evidence from AI inference
  • See affected users, individual occurrences, releases and environments, and a per-user timeline
  • Review projects, aggregate project statistics, bug history and similar-bug matches
  • Get grouped triage views and a recommended critical list of new or regression issues
When to use it
Useful for trying out BugTape's bug-triage workflow without an account, or for letting an assistant explain root causes and fixes from sample captures. It is a demo workspace with sample data, not a place to manage real customer reports.
Requirements
Remote streamable HTTP endpoint; no account, key or environment variables are needed for the demo. Connecting a real app requires signing in with OAuth or running the BugTape connect command.
Before you install
Read-only: acknowledgements, claims and comments are not available. The data is sample shop captures, not real customers. Pointing the assistant at a real workspace instead would expose actual user and session data.

Installation

In SourceWeft

  1. Open BugTape demo in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.bugtape%2Fbugtape-demo/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

14

list_bugs

List Bugs

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.

ParameterslimitoffsetsearchstatusplatformseverityprojectIddeliveryFeed

get_bug

Read an issue

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.

ParametersbugIdrequired

get_bug_events

Read captured events

Get session events for a bug (DOM, network, console, clicks, errors). Prefer passing occurrenceId so events are not mixed across captures.

ParameterstypebugIdrequiredlimitoffsetoccurrenceId

get_repro_context

Read issue evidence

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.

ParametersbugIdrequiredeventLimitoccurrenceId

list_projects

List projects

List all projects in the organization with their bug counts.

Takes no parameters.

get_project_stats

Get Project Stats

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.

ParametersdaysprojectIdrequireddeliveryFeed

get_bug_occurrences

Get Bug Occurrences

List the individual occurrences grouped under a bug. Use this to see which users, sessions, releases, or environments were affected.

ParametersbugIdrequiredlimitoffset

get_bug_users

Get Bug Users

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.

ParametersbugIdrequiredlimitoffset

get_live_occurrences

Get Live Occurrences

Get the most recent occurrences across the organization. Useful for live monitoring and tester workflows. Honors deliveryFeed (tool arg, else PAT / project).

ParameterslimitdeliveryFeed

get_current_org

Current workspace

Return the credential workspace. Agent PATs resolve only their own workspace; human sessions use BUGTAPE_ORG_ID.

Takes no parameters.

get_bug_history

Get Bug History

Get the full audit trail of status/severity changes and assignments on a bug, including who changed what and when.

ParametersbugIdrequired

get_similar_bugs

Get Similar Bugs

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.

ParametersbugIdrequired

list_bug_groups

List Bug Groups

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), browsers/oses, platforms (web/ios/android/react-native/flutter/server — one issue can span several), and anyRegression. Pass both projectId and groupKey as one groupRefs entry to bulk_update_bugs. Legacy groupKeys are accepted only when unique across the organization and are rejected when ambiguous. Prefer this over list_bugs for triage.

ParameterssortlimitoffsetsearchstatusassigneeplatformseveritydirectionprojectIdunresolveddeliveryFeed

Version history

1
  1. v1.0.0LatestOct 26, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Bugtape integrations