Skip to main content

ShakeBugs MCP Server

This MCP server helps you fetch and analyze ShakeBugs user feedback tickets (details + activity history/logs), and provides prompts that guide structured debugging for single or multiple tickets.

Tools​

get_user_feedback_details​

Fetches full ShakeBugs ticket details from a user feedback URL (title, description, device/app info, reproduction steps, and other metadata). This tool is read-only and is typically used as the first step before deeper debugging.

get_user_feedback_activity_history​

Retrieves the ticket’s activity history logs (console output, system events, network requests, errors/stack traces) in chronological order. This tool is read-only and is usually called after get_user_feedback_details when log evidence is needed.

  • Input: issue_url (ShakeBugs URL starting with https://app.shakebugs.com/)
  • Returns: list of log entries (timestamps, levels, messages, network/API failures)
  • Auto-invoked when users ask for “logs”, “activity history”, “console”, “network”, “output”, “stack trace”, or crash timelines (especially with a ShakeBugs link)

Prompts​

analyze_user_feedback_ticket​

A structured workflow for debugging a single ticket:

  • Fetch details with get_user_feedback_details
  • Classify (bug / improvement / question), identify component, and build a timeline
  • If it’s a bug, fetch logs with get_user_feedback_activity_history
  • Correlate logs to the report and provide RCA, evidence, severity, and next steps

batch_user_feedback_analysis​

Analyzes multiple tickets and looks for patterns:

  • Fetch details for each ticket
  • Categorize each (bug / improvement / question)
  • For bug reports, fetch and analyze logs
  • Output a table of findings and highlight cross-ticket trends

Ask questions about your Shake tickets — see examples.