> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.thewhiterabbit.app/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# The White Rabbit MCP: Manage Your Campaigns by Chatting with an AI

The White Rabbit (TWR) has an MCP server that connects your account to AI assistants like Claude. Once connected, you create and manage campaigns, domains, and A/B tests by talking in plain language, and you can also check how your traffic filter is performing without opening the dashboard.

## Before you start

* It works with any AI assistant that supports remote MCP servers. This article uses Claude as the example, but the process is the same elsewhere.
* MCP is available on **every plan**, with up to **5 active keys** per account. What changes is the number of calls per 5-hour window:

| Plan | Calls per 5-hour window |
| ---- |
| Basic and PRO | 50 |
| Freedom | 100 |
| Enterprise | 150 |

## What the MCP can do

The MCP gives your assistant access to the same operations you perform in the dashboard, plus queries about the traffic that went through the filter.

| Area | What the assistant can do |
| ---- |
| **Campaigns** | Search and inspect, create, edit, pause, reactivate, delete, download the integration script, and build the final URL with its parameters |
| **Domains** | List, add, verify, and delete (with the option to migrate campaigns to another domain first) |
| **A/B Storm** | List, inspect, create, edit, pause, reactivate, and delete experiments |
| **Traffic sources** | Check the sources available on your plan |
| **Metrics** | Analyze traffic by country, region, city, device, day, hour, campaign, traffic source, and URL parameters, separating Offer Page, Safe Page, and bots |

Since it is a conversation, you don't need to memorize commands. Just ask for what you want, the way you would ask a person. A few examples to give you an idea of the range:

* "How many bots did I filter in the last 7 days? Break it down by country."
* "Which of my campaigns got the most traffic this week?"
* "Register the domain `home.mydomain.com` and verify it."
* "Give me the full URL, with parameters, for the launch campaign."
* "Pause every campaign pointing to the old offer."
* "Create an A/B Storm with three Offer Pages split 40, 30, and 30."

## Step by step

### 1. Open Integrations in your profile

In the workspace menu, click your profile and open the **Integrations** tab.

![](https://storage.crisp.chat/users/helpdesk/website/-/4/d/7/d/4d7d7d2dfaedd800/01-abrir-integracoes_13c69q0.gif)

### 2. Create your MCP key

On the **MCP** tab, click **New key**, give it a name that identifies where it will be used, and confirm with **Create**.

![](https://storage.crisp.chat/users/helpdesk/website/-/4/d/7/d/4d7d7d2dfaedd800/02-criar-chave-mcp_1ck0xdf.gif)

| The API key and the MCP key are different and cannot replace each other. To connect an AI assistant, always use the key from the **MCP** tab.

### 3. Copy the MCP server URL

TWR shows two fields: the **Key** and the **MCP server URL**. Copy the **URL**, because it already carries your key and is the only thing the assistant needs. Then click **Done**.

![](https://storage.crisp.chat/users/helpdesk/website/-/4/d/7/d/4d7d7d2dfaedd800/03-copiar-url_1oagsks.gif)

||| This is the only time the full key is shown. Copy it and store it somewhere safe before closing the notice. If you lose it, create a new one and revoke the old one.

### 4. Add the server to your AI assistant

In Claude, open **Settings**, go to **Connectors**, click **Add**, and choose **Add custom connector**. Name the connector, paste the URL you copied into the **Remote MCP server URL** field, and confirm with **Add**. The OAuth fields under **Advanced settings** stay empty.

On the connector screen, click **Connect** to activate the connection.

![](https://storage.crisp.chat/users/helpdesk/website/-/4/d/7/d/4d7d7d2dfaedd800/04-adicionar-conector_1r147wi.gif)

For assistants configured through a file, register it as a remote MCP server over HTTP:

```json
{
  "mcpServers": {
    "the-white-rabbit": {
      "url": "https://mcp-server.thewhiterabbit.app/mcp?token=YOUR_KEY"
    }
  }
}
```

| There are no headers, tokens, or separate authentication to set up. The URL already carries your key.

### 5. Confirm the TWR tools showed up

With the connection active, the assistant lists the available tools, split between read-only ones (search campaigns, list domains, query metrics) and write and delete ones (create, edit, pause, delete). If the list appears, everything is working.

![](https://storage.crisp.chat/users/helpdesk/website/-/4/d/7/d/4d7d7d2dfaedd800/05-confirmar-ferramentas_oyoind.gif)

| In Claude, these tools come marked as **Needs approval**, meaning it asks for your authorization before running each one. You can adjust that per tool on the connector screen.

### 6. Make your first request

Start with something simple, like asking for the list of your campaigns or your domains. The assistant queries your account and answers with real data.

![](https://storage.crisp.chat/users/helpdesk/website/-/4/d/7/d/4d7d7d2dfaedd800/06-primeiro-pedido_15g7vs0.gif)

|| To create a campaign, the assistant asks for the domain, the traffic source, and the pages before saving anything. Deletions ask for your explicit confirmation, because they cannot be undone.

### 7. Track your usage and revoke keys when needed

On the same **Integrations** screen, the **MCP usage (5h window)** bar shows how many calls you have used and how long until the limit renews. The list above it shows each key with its creation date and last use.

To disconnect an assistant, click the delete icon in the **Actions** column and confirm the revocation. From that point on, any connection made with that key is rejected.

![](https://storage.crisp.chat/users/helpdesk/website/-/4/d/7/d/4d7d7d2dfaedd800/07-uso-e-revogar_7mms0t.gif)

## Taking care of your key

* The server URL contains your key. Treat it like a password: never post it in group chats, screenshots, or repositories.
* Use one key per place. That way, if you need to cut off access to one, the others keep working.
* Deleted campaigns stop receiving traffic immediately and cannot be recovered. Confirm carefully before approving a deletion. If you only want to stop the traffic for a while, ask to **pause** the campaign instead, which is reversible.
* Metric queries never expose IP addresses, browsers, or request headers, and they only reach campaigns in your own account.

If you would rather integrate your own systems instead of using an AI assistant, TWR also has a REST API, available from the **Freedom** plan up. The full documentation is at [api.thewhiterabbit.app/openapi](https://api.thewhiterabbit.app/openapi), and the key lives on the **API Key** tab, next to the MCP tab.