MCP Setup · Claude Code

Connect Claude Code to Admaxxer

Claude in your terminal — works the same way.

Claude Code (Anthropic's CLI) reads MCP servers from `.claude/settings.local.json` or your user-level config. Paste, then `/mcp` to verify.

Setup walkthrough

1 Generate an MCP token in Admaxxer

Sign in to Admaxxer and open Settings → AI Providers → MCP. Click 'Generate MCP token'. Copy the token immediately — we only store a SHA-256 hash, so the plaintext is shown exactly once. Save it somewhere safe; if you lose it, generate a new one.

2 Add Admaxxer to your Claude Code config

Claude Code reads MCP servers from `.claude/settings.local.json` (project) or `~/.claude/settings.json` (user-wide). Edit whichever scope you want.

code .claude/settings.local.json

3 Paste the Admaxxer MCP server entry

Add an `mcpServers` key with `admaxxer` inside, just like Claude Desktop. The config shape is identical between the two products.

{
  "mcpServers": {
    "admaxxer": {
      "url": "https://admaxxer.com/mcp/sse",
      "transport": "sse",
      "headers": {
        "Authorization": "Bearer mcp_ADM_<paste_token_here>"
      }
    }
  }
}

4 Verify with /mcp inside Claude Code

Run the `/mcp` slash command in Claude Code. You should see `admaxxer` listed with status `connected` and 6 tools. If it shows `failed`, double-check the bearer token and the SSE URL.

5 Verify the connection

Ask your AI 'What ad accounts do I have connected?' If it lists your Meta + Google connections, you're done. If it says it doesn't have access to that information, see the Troubleshooting section below — most often a stale config or an unrestarted client.

Try these prompts after setup

Once Claude Code is connected, ask it any of these — the answers come straight from your Admaxxer workspace.

Pro tip: Add a custom slash command at `.claude/commands/admaxxer.md` that always pulls in the Admaxxer system context — saves typing on every session.

Tools your AI can call

Admaxxer's MCP server exposes 6 tools. Read tools run automatically; write tools (pause / update_campaign) require explicit user confirmation in Admaxxer.

admaxxer_list_connectionsread

Lists every Meta + Google ad-platform connection in the workspace, with status (healthy / token expired / disabled), platform, and account label. Used by the AI to discover which connections to query for insights.

Example prompt: “What ad accounts do I have connected?”

admaxxer_list_campaignsread

Lists active or paused campaigns for a given connection (Meta or Google). Returns campaign ID, name, objective, status, daily budget, and lifetime spend.

Example prompt: “Show me all my Meta campaigns sorted by spend.”

admaxxer_get_campaign_insightsread

Pulls metrics for one campaign over a date range — impressions, clicks, spend, conversions, ROAS, CPA. Optional breakdowns by age, gender, device, region.

Example prompt: “How did campaign 'BFCM Scale' perform last week?”

admaxxer_get_account_insightsread

Account-level rollup of insights across all campaigns for a connection. Optional breakdowns. Best for high-level ROAS / spend trends.

Example prompt: “What's my Meta account ROAS for the last 30 days?”

admaxxer_query_metricsread

Runs a whitelisted Tinybird analytics pipe (visitors, revenue, MER, LTV, MMM, attribution, forecast). The workspace_id is injected server-side — the AI cannot see another workspace's data.

Example prompt: “What's my blended MER for the last 14 days vs the prior 14 days?”

admaxxer_get_workspace_contextread

Returns the workspace's plan tier, currency, time zone, connected platforms, and last-sync timestamps. Useful for the AI to ground its answers.

Example prompt: “What plan am I on and when was my data last synced?”

Troubleshooting

401 Unauthorized when the client first connects

Your token has been revoked or expired. Open Admaxxer → Settings → AI Providers → MCP and generate a fresh token. Replace the value in your client's config file and restart the client.

The Admaxxer tools don't show up in the tool picker

Most MCP clients only read the config file at startup. Fully quit the client (not just close the window) and reopen it. In Cursor, Cmd-Shift-P → Reload Window. In Claude Desktop, Cmd-Q then relaunch.

Rate-limit errors on heavy questions (HTTP 429)

Tinybird-backed pipes are rate-limited per token to protect the analytics layer. Spread the call out (`for the last 7 days` instead of `the last 90 days hourly`) or wait 30 seconds and retry. Free workspaces share a tighter bucket than paid.

Tool result says 'Connection does not belong to this workspace'

You issued the MCP token from a workspace that doesn't have the ad connection wired up. Switch to the right workspace in Admaxxer (top-left switcher), reissue the token, and update the client config.

Destructive tool calls (pause / update_campaign) aren't running

By design — write tools require explicit confirmation in Admaxxer's UI. Open `/chat` in Admaxxer; the agent will surface a confirm card with the exact action. The same confirmation flow applies to MCP-initiated writes.

Other AI clients

Ready to connect?

Generate an MCP token in Admaxxer, paste it into Claude Code's config (.claude/settings.local.json (project) · ~/.claude/settings.json (user)), and your AI is wired into every ad account in this workspace.

Generate your MCP token