Connect RAVE™ to Claude

Connect RAVE™ to Claude and ask questions like "Which campaign got the most sign-ups last week?" or "Why isn't my card showing on this page?". Claude reads your RAVE™ data through the RAVE™ connector and answers with real numbers from your account.

The connector is read-only: Claude can read your sites, campaigns, analytics and recent events, and check pages, but it can't change anything in RAVE™. Open Settings → Connect to Claude in any workspace (or go to /app/connect-claude) for the URL, your API keys and the activity log.

What Claude can see

Claude sees exactly what you can see in RAVE™, nothing more:

• Your workspaces only. Every workspace you belong to (through the account team or as a direct member). Agency owners and staff see their client workspaces; a client login sees only its own workspace.
• Not Installer workspaces. Where your role is Installer, Claude sees the workspace name and your role, and no campaign or analytics data.
• No platform admin access. If you're on the RAVE™ platform team, the connector still only shows the accounts you belong to as a customer.
• No emails. Recent events show a first name and last initial, product, step label, source and time. Never an email address or anything that identifies a person beyond that.
• No webhook keys. Campaign settings never include the webhook URL's key.

Access follows your role live: if you leave a workspace or your role changes, Claude's access changes on its next request.

Connect Claude.ai (and the Claude desktop and mobile apps)

1. 1

   Copy the URL

   In RAVE™, open Settings → Connect to Claude and copy the connector URL: https://rave.cxformula.com/api/mcp.

2. 2

   Add the connector

   In Claude, open Settings → Connectors, click Add custom connector, name it RAVE™ and paste the URL. (On Team and Enterprise plans, an owner may need to add it for the organization first.)

3. 3

   Sign in

   Click Connect. A RAVE™ window opens. Enter your email and click Email me a link, then type the 6-digit code from the email into that same window and click Sign in with code. (The email's link would open in your mail app or another browser, outside Claude's window, so use the code here.)

4. 4

   Review and allow

   The consent screen lists every workspace you're sharing (and any Installer workspaces that aren't shared). Click Allow.

5. 5

   Ask away

   In a chat, make sure RAVE™ is turned on in the tools menu, then ask a question.

Connect Claude Code

Run this in your terminal, then sign in when your browser opens:

claude mcp add --transport http rave https://rave.cxformula.com/api/mcp

For scripts, CI or other MCP clients that can't open a browser, use a personal API key instead:

claude mcp add --transport http rave https://rave.cxformula.com/api/mcp --header "Authorization: Bearer rave_pat_..."

Personal API keys

1. 1

   Create a key

   In Settings → Connect to Claude, under Personal API keys, name the key (for example "Claude Code on my laptop"), pick when it expires (30 days, 90 days, 1 year or never) and click Create key.

2. 2

   Copy it now

   The key (it starts with rave_pat_) is shown once. RAVE™ keeps only a fingerprint of it, so it can't show it again. The page also gives you the Claude Code command with the key filled in.

3. 3

   Revoke when done

   Click Revoke next to a key and it stops working on the next request.

A key acts as you, with your access at the time of each request, across all your workspaces. You can have up to 10 active keys. Treat a key like a password: don't paste it into shared documents or commit it to code.

Example questions

• "Which campaign got the most sign-ups in the last 7 days?"
• "Compare paid and organic step labels this month." (uses the same filters and comparisons as the Analytics dashboard)
• "How did this month compare with last month, in percent?"
• "Why isn't my card showing on https://go.example.com/join?"
• "Is the pixel installed on all my sites? Which ones haven't sent a page view lately?"
• "List my active campaigns and the pages they show on."
• "Show me the last 10 purchases for the Kit campaign."
• "For my agency, compare sign-ups by client for last month."

Why isn't my card showing?

Give Claude the full page address. It checks the page the same way the pixel does, in order:

1. The site. Is there a RAVE™ site for this domain? Each domain and subdomain needs its own site (or a shared campaign).
2. Paused. Is the workspace over its visitor limit, beyond its site limit or without an active plan?
3. The pixel. Has RAVE™ received page views from this site, and from this exact page, recently?
4. Page rules. Which active campaigns' Show on and Hide on rules match the page, including rules limited to one domain ("only on go.example.com").
5. Cards. For each card: is it on, does its own page targeting match, and does it have enough events (or visitors) in its time window? Test events count for an hour on RAVE™ Alert and Live cards and never on RAVE™ Count.

Claude then tells you in plain English what will show, or what to fix.

Activity and privacy

Every request Claude makes is logged with who made it, the tool, the workspace, the time and whether it worked. What came back is never stored. You see your own requests under Activity on the Connect to Claude page; account owners see every request in their account.

Requests are rate limited per person and per key (short bursts are fine; very heavy use waits a moment).

Disconnect

• Claude.ai: remove the connector in Claude's Settings → Connectors, or click Disconnect under Connected apps in RAVE™.
• API keys: click Revoke next to the key.

Troubleshooting