> For the complete documentation index, see [llms.txt](https://docs.arcade.software/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcade.software/kb/interactive-demo/leverage/mcp/use-cases.md).

# Use Cases

### How can teams use MCP for analytics?

MCP lets you ask questions about your Arcade performance using natural language. Examples:

* "How is my demo performing?"
* "What are my top demos this month?"
* "Where are users dropping off?"
* "Which companies engaged with my demos?"

***

### Can MCP turn my data into charts or reports?

Yes. Your AI assistant can help structure and visualize your Arcade data — plays over time, completion trends, drop-off points, top performing Arcades.

Example prompt:

* "Chart my top demos from the last 30 days."

***

### Can MCP help identify buyer interest?

Yes. Use engagement data to understand what buyers or customers care about most — useful for prioritizing follow-ups, spotting buying signals, and identifying product interest.

***

### Can I use MCP to find relevant Arcades?

Yes. You can search your Arcade library using natural language.

Example prompts:

* "Show me demos related to onboarding."
* "Find demos for this feature."
* "Which Arcades mention customer success?"

Useful for sales, enablement, and internal discovery.

***

### Can MCP recommend how to improve demos?

Yes. Your AI assistant can analyze performance data and suggest improvements — a stronger opening step, a shorter flow, better CTA placement, or clearer messaging.

Example prompt:

* "How can I improve this demo based on performance?"


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.arcade.software/kb/interactive-demo/leverage/mcp/use-cases.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
