> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/faq/marketing-optimization/connect-claude-to-the-data-assistant.md).

# Connect Claude to the Data Assistant

Connect Claude to your AdPage account through the AdPage MCP server. Claude signs in with OAuth, so there is no token to copy. It can then query your GA4, Google Ads, Meta Ads, TikTok, LinkedIn, Magen

***

### What is the AdPage × Claude integration?

[Claude](https://claude.ai/) is Anthropic's AI assistant. Add the AdPage MCP server as a **connector** and Claude gets direct access to the same tools as the Data Assistant:

* Server-side tracking data from ClickHouse, including outgoing and incoming requests and webhook logs
* GA4, Google Ads, Meta Ads, TikTok, and LinkedIn data
* Magento and Shopify data, including orders, inventory, and marketing
* Attribution reports, funnels, and data quality checks
* GTM container audits and consent mode validation

> 🔐 **No token to copy.** Claude signs in through OAuth. You add one URL, log in with your AdPage account once, and Claude keeps the connection. Nothing secret ends up in the URL, so there is no token to leak, rotate, or accidentally paste into a shared document.

> 💡 **Difference from Manus MCP:** With Claude you ask a question and get an answer in the conversation. It is fast and interactive, which makes it the better fit for exploring. Manus runs an entire workflow unattended and hands back a finished document. See [Connect Manus AI to the Data Assistant](/faq/marketing-optimization/connect-manus-ai-to-the-data-assistant.md).

***

### What do you need?

Before you start, make sure you have:

* An active **AdPage account** with at least one container
* A **Claude account** — Free, Pro, Max, Team, or Enterprise
* Two minutes

> ⚠️ **Team and Enterprise plans:** Only an owner or admin can add a connector for the whole organization. On a personal plan, you add it for yourself.

***

### The AdPage MCP server URL

One URL works for every Claude surface — web, desktop, and Claude Code:

```
https://mcp.adpage.io/mcp
```

You can also copy it inside AdPage. Sign in at [data.adpage.io](https://data.adpage.io/), select **Integrations** in the left menu, scroll to **Account integrations**, and select the **Claude (MCP)** card.

***

### Step 1: Open Connectors in Claude

1. Sign in at [claude.ai](https://claude.ai/), or open the Claude desktop app.
2. Select your **profile icon** and then **Settings**.
3. Select **Connectors** in the sidebar.
4. Select **Add custom connector**.

***

### Step 2: Add the AdPage server

Enter the connector details.

| Field                     | Value                       | Description                                      |
| ------------------------- | --------------------------- | ------------------------------------------------ |
| **Name**                  | `AdPage`                    | Any recognizable name, such as `AdPage`          |
| **Remote MCP server URL** | `https://mcp.adpage.io/mcp` | The same URL for every account — no token, no ID |

Select **Add**.

> 💡 **No advanced settings needed.** Leave the OAuth client ID and client secret fields empty. The AdPage server registers Claude automatically, so you do not have to create credentials yourself.

***

### Step 3: Sign in with your AdPage account

1. Select **Connect** on the AdPage connector.
2. An AdPage login window opens. Sign in with your normal AdPage account.
3. Confirm the access request.

Claude stores the connection and shows AdPage as **Connected**. You only do this once — Claude refreshes its own access in the background.

> 🔎 **What happens here:** This is a standard OAuth 2.0 authorization code flow with PKCE. Claude registers itself with the AdPage server, sends you to the AdPage login, receives a short-lived code, and exchanges that for an access token and a refresh token. Those tokens are stored in your Claude account and are tied to your AdPage user, so the audit trail stays traceable per person.

***

### Step 4: Test the connection

1. Open a **new chat** in Claude.
2. Make sure the **AdPage** connector is enabled for the conversation. You will find it under the tools or attachments menu in the message box.
3. Ask a simple question, such as:

   > *Which containers are available in my AdPage account?*
4. Claude calls `list_containers` and returns your containers.

Does it work? Try something larger:

> *Take my main container. Compare Google Ads spend, conversions and ROAS of the past 30 days with the 30 days before that, and tell me which campaigns got worse.*

Claude picks the container, retrieves the data, compares the periods, and explains the result in the conversation.

***

### Claude Code

Claude Code uses the same server. Add it from the terminal:

```bash
claude mcp add --transport http adpage https://mcp.adpage.io/mcp
```

Then run `/mcp` inside Claude Code and select **adpage** to sign in. The same OAuth flow opens in your browser.

To share the server with everyone working in a repository, commit an `.mcp.json` in the project root instead:

```json
{
  "mcpServers": {
    "adpage": {
      "type": "http",
      "url": "https://mcp.adpage.io/mcp"
    }
  }
}
```

Each person still signs in with their own AdPage account, so the file holds no secrets and is safe to commit.

***

### What can you ask?

| Question                                                                  | What Claude uses                  |
| ------------------------------------------------------------------------- | --------------------------------- |
| *Which channel brought in the most revenue last month?*                   | Attribution and revenue reports   |
| *Show the conversion funnel for my webshop over the past 14 days.*        | Funnel analysis                   |
| *Are there any tracking errors in my container?*                          | Data quality and platform health  |
| *Check my GTM container for consent mode problems.*                       | GTM audit and consent validation  |
| *Which products went out of stock while they were still getting traffic?* | Shopify or Magento inventory data |
| *Compare Meta Ads and Google Ads performance per device.*                 | Platform reports                  |

***

### Common issues

#### The connector does not appear in my chat

Connectors are enabled per conversation. Open the tools or attachments menu in the message box and switch **AdPage** on. On a Team or Enterprise plan, an admin may need to allow the connector for the organization first.

#### “Could not connect” when adding the connector

Check that the URL is exactly `https://mcp.adpage.io/mcp`, with no trailing slash, no `?token=` behind it, and no extra spaces. The Claude connector uses OAuth, so it does not need a token in the URL — a Manus-style URL with a token will not work here.

#### The login window opens but nothing happens

Your browser is probably blocking the pop-up, or you are signed in to a different AdPage account in that browser. Allow pop-ups for claude.ai, sign out of the other account, and select **Connect** again.

#### Claude does not use AdPage automatically

Claude decides per question whether a connector is relevant. Name it explicitly when it does not:

> *Use the AdPage connector to …*

#### “Unauthorized” after it worked before

Your access was revoked or expired. Open **Settings → Connectors** in Claude, disconnect AdPage, and connect again.

#### I do not see data from a platform

AdPage MCP only returns data from integrations connected to your AdPage container. In **Integrations → Container integrations**, check that the platform is active for the container you are asking about. This includes Google Analytics, Google Ads, Meta Ads, TikTok, LinkedIn, Magento, and Shopify.

***

### Security and best practices

* **Everyone connects with their own account.** The connector carries no shared secret, so each person signs in as themselves and sees only the containers they already have access to in AdPage.
* **Revoke access during offboarding.** Removing someone from AdPage also ends their Claude connection. There is no separate token to hunt down.
* **The MCP is mostly read-only.** Claude cannot modify GTM containers through MCP. That changes only if you explicitly enable write permissions in AdPage, and those actions require approval.
* **Check what you share.** Answers can contain revenue and customer figures. Treat a Claude conversation like any other document with company data.


---

# 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.adpage.io/faq/marketing-optimization/connect-claude-to-the-data-assistant.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.