What this is

Campaignly publishes an MCP server at https://campaignly.net/api/mcp. Once connected, you can ask Claude questions about your campaigns, clients, audits, SEO data, Google Ads, Search Console, and GA4 — and have Claude render the answer as a live, interactive artifact inside the chat. No CSV exports, no manual screenshots, no copy-paste.

Everything is read-only today. Claude reports on your data; it can't change it.

What you'll need

• A Campaignly account
• Either Claude.ai (Pro or Max), Claude Desktop, Claude Code, or direct Anthropic API access
• About 2 minutes to generate a key and paste it into Claude

Using it with live artifacts

This is what most people connect for: ask a question, get an interactive dashboard back.

Claude can call Campaignly's tools to fetch your real data, then build a React artifact you can sort, filter, and copy from — all in the same conversation.

Three prompts that work today:

Performance dashboard

"Find my Acme Inc campaign and pull the last 30 days of ad performance. Render it as a dashboard with KPI tiles at the top and a daily trend chart below."

Claude looks up the campaign, finds the linked ad accounts, pulls daily metrics, and renders an artifact. If Claude tries to make up numbers, tell it: "Use the tools — don't fabricate."

SEO opportunity table

"Show me all my SEO quick-win opportunities as a sortable table with priority and estimated traffic. I want to share this view with my client."

Claude pulls the opportunity list and builds a sortable, filterable table you can paste into a doc.

Google Ads waste audit

"Find Google Ads search terms with high cost and zero conversions in the last 90 days. Build me an artifact summarising the wasted spend and the worst offenders."

Claude pulls the search terms report, filters to zero-conversion spend, and renders a tidy waste breakdown.

Artifacts can be re-opened from your chat history, so a single conversation gives you a re-usable view your client never sees the chat behind.

What Claude can see

Claude only sees what your Campaignly account can see — your campaigns, your clients, your connected Google accounts. Other workspaces and other users are invisible.

You choose which permissions to grant when you connect:

| Permission | What it covers | |---|---| | Base (always on) | Campaigns, clients, proposals, content calendar, audits, SEO data, team, activity, billing | | Google Ads | Your Google Ads accounts, campaigns, keywords, search terms, performance breakdowns | | Google Search Console | Your GSC properties: top queries, top pages, indexing, URL inspection | | Google Analytics 4 | Your GA4 properties: traffic, events, conversions, ecommerce, audiences |

You can grant or revoke any of these from Account → API Keys in Campaignly. Every tool call is recorded in your audit log, so you always have a record of what Claude looked at.

Connect Claude to Campaignly

There are two paths. Pick whichever matches your setup.

Path A — Claude Desktop, Claude Code, or the Anthropic API

Best for: anyone who uses Claude Desktop on Mac/Windows, the Claude Code CLI, or builds with the Anthropic API directly. Works on every plan.

1. In Campaignly, go to Account → API Keys (https://campaignly.net/dashboard/account/api-keys)
2. Click Create new key
3. Tick the Google permissions you want (Ads, Search Console, Analytics) — base permissions are always included
4. Copy the key (it starts with clk_). You'll only see it once
5. In your Claude client, add Campaignly as an MCP server. For Claude Desktop, edit claude_desktop_config.json:

{
  "mcpServers": {
    "campaignly": {
      "type": "http",
      "url": "https://campaignly.net/api/mcp",
      "headers": { "Authorization": "Bearer clk_..." }
    }
  }
}

6. Restart Claude Desktop. The Campaignly tools show up in the tool list

For Claude Code or the API, set the same Authorization: Bearer clk_... header on your MCP transport.

Path B — Claude.ai web (Pro or Max plan)

Best for: chatting in your browser. Requires a Claude.ai Pro or Max plan with custom connectors enabled.

1. In Claude.ai, open Settings → Connectors → Add custom connector
2. Paste the URL: https://campaignly.net/api/mcp
3. Click Connect. You'll be sent to Campaignly to sign in
4. On the consent screen, tick the Google permissions you want
5. Click Approve. You're returned to Claude.ai with the connection active

Refresh tokens rotate automatically. You won't be asked to reconnect every hour.

Rate limits

Each connection has a budget:

• 300 credit-weighted units per minute
• 500 credit-weighted units per day

Most tool calls cost 1 credit. Larger calls — daily breakdowns, full audits, deep performance reports — cost 5 credits. If Claude hits the limit, it gets a polite "try again in N seconds" response and waits. You don't have to babysit it.

For heavy work, chain a few short prompts instead of one mega-prompt — Claude will be smarter about reusing earlier results.

Example prompts to try

Copy-paste any of these into Claude once you're connected:

1. "Summarise my last completed campaign and its KPIs against targets."
2. "Which of my clients haven't had a touchpoint in the last 30 days?"
3. "Build a competitive snapshot for my top SEO competitor — shared keywords, gaps, AI visibility."
4. "Show me Google Ads keywords with quality score 4 or below as a table."
5. "Render a weekly review artifact: active campaigns, content scheduled, audits run."

Troubleshooting

"Insufficient scope" or "Not authorised" Reconnect the connector and tick the Google permission for whichever tool family you're using. If you created your key before May 2026, you have all Google permissions automatically — but new keys require an explicit opt-in.

"Not connected to Google Ads" (or GSC, or GA4) You need to connect the source platform to Campaignly first. Go to Integrations in Campaignly and connect the platform, then ask Claude again.

Rate-limited (429) Wait the suggested retry interval. For ongoing heavy use, break the work into smaller prompts — Claude will reuse intermediate results without burning more budget.

Claude is making up numbers Tell it to "use the Campaignly tools and don't fabricate." It will call the tools and re-answer from real data.

Revoking a connection

Open Account → API Keys in Campaignly and click Revoke on the key. The next time Claude tries to call a tool with that key, it will get a 401 and report it back to you. Your conversation history stays, but the tools stop working until you connect a new key.

What's next

• Want Claude to write back to Campaignly (create campaigns, draft proposals, schedule content)? That's on the roadmap; today's MCP is read-only by design.
• Connecting Google Ads — needed for the Google Ads tools
• Connecting Google Search Console — needed for the GSC tools
• Connecting Google Analytics 4 — needed for the GA4 tools

Connect Claude to Campaignly now → Open API Keys