# Use Cases & Workflows

Real-world workflows for mobile debugging with Luciq MCP. Each workflow is a sequence of natural language prompts you can use directly in your IDE.

***

## Investigate a Production Crash

When a crash spikes in production, go from alert to root cause without leaving your editor.

**Prompt sequence:**

1. "Show me the top 5 crashes in production this week"
2. "Get details for crash #\[number] - show me the stack trace"
3. "Show crash patterns by device for this crash"
4. "List the most recent occurrences"
5. "Show occurrence details for \[token] - what device and OS?"

{% embed url="<https://streamable.com/ekvoh8>" %}

**Tools used:** `list_crashes` > `crash_details` > `crash_patterns` > `list_occurrence_tokens` > `get_occurrence_details`

**What you get:** The full picture - from which crashes matter most, to the exact stack trace, to which devices and OS versions are affected, down to the specific session that triggered it.

***

## Daily App Health Check

Start your morning with a quick stability check across all your apps.

**Prompt sequence:**

1. "List my applications"
2. "Show production crashes from the last 24 hours for \[app name]"
3. "Are there any new app hangs this week?"
4. "Show me recent 1-star reviews"

**Tools used:** `list_applications` > `list_crashes` > `list_application_hangs` > `list_reviews`

**What you get:** A fast overview of crashes, hangs, and user sentiment - all without opening the dashboard.

***

## Regression Check After a Release

Just shipped a new version? Verify nothing broke.

**Prompt sequence:**

1. "Show crashes for version \[X.Y.Z] in production"
2. "Are any of these crashes new to this version?"
3. "Show crash patterns by app version for crash #\[number]"
4. "Are there any app hangs specific to version \[X.Y.Z]?"
5. "Show 1-2 star reviews for version \[X.Y.Z]"

**Tools used:** `list_crashes` (with version filter) > `crash_patterns` > `list_application_hangs` > `list_reviews`

**What you get:** A release-specific stability report showing whether your new version introduced regressions or new crash patterns.

***

## Triage User-Reported Bugs

Review and prioritize bug reports submitted by your users through the Luciq SDK.

**Prompt sequence:**

1. "Show me open bugs for \[app name] sorted by priority"
2. "Get details for bug #\[number]"
3. "What device and OS was the user on?"
4. "Are there any crashes related to the same screen or view?"

**Tools used:** `list_bugs` > `bug_details` > `list_crashes` (cross-reference by view)

**What you get:** Full bug context including device info, user steps, and whether the bug correlates with known crashes.

***

## Analyze App Store Sentiment

Monitor what users are saying about your app and correlate feedback with stability data.

**Prompt sequence:**

1. "Show me recent app store reviews"
2. "Filter to 1-2 star reviews from the last month"
3. "Are there any crashes that could explain the negative reviews?"
4. "Show me reviews for version \[X.Y.Z] specifically"

**Tools used:** `list_reviews` > `list_crashes` (cross-reference)

**What you get:** User sentiment tied to app versions, with the ability to cross-reference negative reviews against crash data.

***

## Device-Specific Investigation

A QA engineer reports issues on a specific device model. Investigate with MCP.

**Prompt sequence:**

1. "Show crashes on Samsung Galaxy S24 in production"
2. "Break down crash #\[number] by OS version"
3. "Show occurrence details for a Galaxy S24 occurrence"
4. "Are there app hangs on this device?"

**Tools used:** `list_crashes` (with device filter) > `crash_patterns` > `get_occurrence_details` > `list_application_hangs`

**What you get:** A device-specific stability profile showing which crashes and hangs concentrate on that hardware.

***

## Pre-Release QA Check

Before pushing to production, check the stability of your beta or staging builds.

**Prompt sequence:**

1. "Show crashes in the beta environment for the last 7 days"
2. "Are there any app hangs in staging?"
3. "Show me bug reports from beta testers this week"
4. "What are the top crashes by occurrence count in beta?"

**Tools used:** `list_crashes` (beta/staging mode) > `list_application_hangs` > `list_bugs`

**What you get:** A pre-release stability snapshot so you can catch issues before they reach production.

***

## Tips for Better Results

{% hint style="info" %}
**Be specific about time ranges.** "Last 7 days" or "since March 1" gives more targeted results than "recent."

**Specify the environment.** "Production" vs "beta" vs "staging" helps target the right data.

**Use app names.** If you have multiple apps, mention which one by name or slug.

**Chain your queries.** Start broad (`list_crashes`) then narrow (`crash_details` > `crash_patterns` > occurrence). Each answer gives you context for the next question.

**Ask follow-up questions.** MCP tools work well in conversation. Your AI assistant retains context from previous queries in the same session.
{% endhint %}

***

## What's Next?

* [**Tools Reference**](/product-guides-and-integrations/product-guides/ai-features/luciq-mcp-server/mcp-tools-reference.md) - Full documentation for all 10 tools with parameters and response fields
* [**FAQ & Troubleshooting**](/product-guides-and-integrations/product-guides/ai-features/luciq-mcp-server/faq-and-troubleshooting.md) - Common issues and how to resolve them


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.luciq.ai/product-guides-and-integrations/product-guides/ai-features/luciq-mcp-server/use-cases-and-workflows.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.