> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clarityq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Using ClarityQ from AI Assistants

> How to ask ClarityQ questions from Claude and other MCP clients — products, long answers, clarifying questions, follow-ups, and usage.

Once the ClarityQ MCP server is [connected](/integrations/clarityq-mcp-server/connecting-ai-assistants), you can ask your assistant business questions in plain language and it asks ClarityQ for the answer. ClarityQ runs the question exactly like [Ask Anything](/ask-anything/asking-questions): same Context Layer, same data warehouse, same permissions.

## Available Tools

The server gives your assistant two tools:

| Tool | What it does |
| - | - |
| `list_products` | Lists the ClarityQ products you can ask about, grouped by organization. Workspaces show their member products. |
| `ask_question` | Asks ClarityQ a question about one product and returns the answer. |

Both tools only read data. They never change your Context Layer, dashboards, or settings.

## Choosing a Product

Every question runs against one product. Name it in your message — for example, *"Using ClarityQ, what was weekly active users for Star Surge last week?"*

If you don't name a product, or the name matches more than one, your assistant can call `list_products` and ask you which one you mean.

## What an Answer Contains

Each answer includes:

* **The answer** as text, with tables where the data calls for them.
* **The SQL ClarityQ ran**, so you or your assistant can check how the numbers were calculated.
* **An Open in ClarityQ link** to the same conversation in the ClarityQ app.

Answers through the MCP server don't include ClarityQ visualizations or dashboards. Your assistant can build its own charts from the data in the answer, or you can open the conversation in ClarityQ.

## Long Answers

Some questions take several minutes to answer. If an answer isn't ready yet, ClarityQ tells your assistant it's still working, and the assistant asks again to pick up the result. ClarityQ keeps working on the question in the meantime, so nothing is lost.

While a question runs, some assistants (for example Claude Code) show progress updates such as *Running SQL on the warehouse…*.

## Clarifying Questions

When a question is ambiguous, ClarityQ may ask for clarification — for example, which revenue definition to use. Your assistant shows you ClarityQ's question and options. Your reply goes back to ClarityQ and the answer continues from there.

## Follow-up Questions

Follow-up questions continue the same ClarityQ conversation, so ClarityQ keeps the earlier context. To make sure your assistant continues the conversation rather than starting a new one, say so — for example, *"Follow-up in the same ClarityQ conversation: how does that compare to the week before?"*

Every conversation started from an assistant also appears in your Ask Anything history in ClarityQ.

## Workspaces

A workspace answers across several member products. When you ask a workspace, ClarityQ uses its default member products unless you name the ones you want — for example, *"Ask the Lobby workspace, using Coffee Mania and Tea Time only"*. The answer lists which members it used and which others you can include. The members you choose stay fixed for that conversation.

## Usage

Questions asked through the MCP server count toward your organization's usage the same way as questions asked in the ClarityQ app, in prompts or CQT depending on your plan. On the Usage page they appear under their own **MCP** type, so you can see how much of your usage comes from AI assistants.

## Permissions

Your assistant acts as you. It can only reach the products you can access in ClarityQ, and your role decides what it can do — the same rules as in the ClarityQ app. Only products of organizations with MCP access turned on are available.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.