> For the complete documentation index, see [llms.txt](https://docs.zenlytic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zenlytic.com/mcp/connecting-to-zenlytic/claude-ai.md).

# Claude.ai

Connect Claude.ai to Zenlytic's MCP server so Claude can query your business data directly.

Claude.ai support MCP custom connectors with OAuth out of the box, so this is one of the easiest clients to connect to Zenlytic. See [MCP Server](/mcp/connecting-to-zenlytic.md) for what you get once connected and general prerequisites.

## Before you start

You'll need the MCP URL that matches your Zenlytic instance:

* If you sign in at `app.zenlytic.com`, use `https://mcp.zenlytic.com/mcp`.
* If you sign in at `eu.zenlytic.com`, use `https://mcp-eu.zenlytic.com/mcp`.
* If your organization uses a company-specific URL on the US instance, use `https://<company>.mcp.zenlytic.com/mcp`. For example, Acme would use `https://acme.mcp.zenlytic.com/mcp`.
* If your organization uses a company-specific URL on the EU instance, use `https://<company>.mcp-eu.zenlytic.com/mcp`. For example, Acme would use `https://acme.mcp-eu.zenlytic.com/mcp`.

If you're unsure which Zenlytic instance your organization uses, ask your Zenlytic administrator.

## Connect with OAuth (recommended)

1. Open **Settings → Connectors**
2. Click **Add**, then choose **Add custom connector**.
3. Paste in the MCP URL for your Zenlytic instance and click **Add**.
4. Click **Connect**, complete the OAuth login/approval flow in the browser window that opens, and pick your workspace.

Your connector is now authorized — you won't need to log in again unless you revoke access.

## Connect with a Personal Access Token (alternative)

If OAuth isn't available, you can authenticate with a static token instead. Creating one requires the Admin (or Organization Admin) role — see [Option 2](/mcp/connecting-to-zenlytic.md#option-2-connect-with-a-personal-access-token-for-static-config-clients-or-when-oauth-isnt-available).

1. In Zenlytic, go to **Settings → Profile → Personal Access Tokens** (`/personal-access-tokens`), click **Create token**, and copy it immediately — it's only shown once.
2. In the **Add custom connector** dialog, open **Advanced settings**.
3. Add a request header named `Authorization` with the value `Bearer <your-personal-access-token>`, and mark it required.
4. Click **Add**, then **Connect**.

## Using it

Once connected, ask Claude a data question naturally, for example:

> "Hey Zoë, who were our top 5 customers by revenue last month?"

Claude will call the `ask_zoe` tool and return the answer along with a link back to the full conversation in Zenlytic.


---

# 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.zenlytic.com/mcp/connecting-to-zenlytic/claude-ai.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.