Skip to content

Blog

AdCrunch Is Now in the Claude Connectors Directory

AdCrunch is in the Claude Connectors Directory. Connect it from Claude with no server URL, then read Meta, TikTok, Google Ads and OpenAI performance and change Meta campaigns.

Product updates

A grid of connector tiles with one tile checked in lime, beside the headline "Now in the Claude Connectors Directory", on the AdCrunch dark-lime card.

AdCrunch is now in the Claude Connectors Directory. You find it inside Claude, you click Connect, and you sign in. You do not copy a server URL anymore.

Open AdCrunch in the directory →


Connect AdCrunch From the Directory

You need an AdCrunch account first. Start the 7-day trial if you do not have one.

On claude.ai or in Claude Desktop:

  1. Go to Customize → Connectors, and click the + next to Connectors.
  2. Find AdCrunch in the list. You can also open claude.ai/directory/adcrunch.
  3. Click Connect. Your browser opens the AdCrunch sign-in. Sign in and approve the access.
  4. In a chat, click +, then Connectors, and turn on AdCrunch for that chat.

Then ask Claude: List my advertisers.

On a Team or Enterprise plan, an Owner adds AdCrunch first. The Owner goes to Organization settings → Connectors, clicks Browse connectors, selects AdCrunch and clicks Add to your team. Each member then connects with their own AdCrunch sign-in.

After you connect on claude.ai or in Claude Desktop, AdCrunch is also in the Claude mobile apps the next time you sign in there.

If you belong to more than one AdCrunch organization, Claude acts for the organization that is active in your most recent AdCrunch session. Auth & scopes tells you how to choose it.


What Claude Can Do With AdCrunch

Ask Claude to… What happens
Read your accounts Claude reads setup and performance on Meta, TikTok, Google Ads and OpenAI.
Build on Meta Claude creates campaigns, ad sets, creatives and ads. Each campaign, ad set and ad starts paused.
Change what runs on Meta Claude pauses, activates, archives, copies and renames, and changes budgets, bids and schedules. Some of these changes wait for you.
Target on Meta Claude targets interests and job titles, and builds website, customer-list and lookalike audiences.
Show the ad Claude gets the ad as Meta renders it in the Feed, Stories and Reels of Facebook and Instagram, before the ad goes live.
Plan the quarter Claude drafts a Campaign Plan. You approve it.
Run your playbook Claude runs a saved Skill by name.

What a Person Still Decides

Claude can change a live ad account. So a person confirms each change that can raise your spend. A person also confirms an archive, because you cannot undo it.

Four Changes Wait for Your Confirmation

When Claude asks for one of these changes on Meta, the change waits:

  • An activate. It turns on a campaign, an ad set or an ad, so spend starts.
  • An archive. An archived campaign, ad set or ad cannot go back into delivery.
  • A budget increase.
  • A schedule change of an active ad set that can extend its delivery (a later end time, no end time, or an earlier start time).

Claude gives you a link to the change. You open it in the AdCrunch console, read what the change does, and click Confirm or Reject. The sidebar shows how many changes wait. Claude cannot confirm its own change.

When nobody decides within 24 hours, the change expires. AdCrunch then sends nothing to Meta. After you confirm, AdCrunch reads the ad account again before it applies the change. The ad account can be different from when Claude asked.

Other Changes Apply at Once

A pause, a budget decrease, a bid change, a rename, a create and a copy do not wait. A pause lowers spend. A bid change does not raise the budget. Each campaign, ad set and ad that Claude creates or copies starts paused, so it spends nothing until you confirm its activate.

Only a Person Approves a Campaign Plan

Claude drafts and edits a Campaign Plan. It cannot approve the Campaign Plan, and it cannot validate a Line Item. You do that on the page of the Campaign Plan, in the AdCrunch console. An approval records your decision. The Meta tools do not check it.

Every Change Is on the Activity Page

The Activity page lists each change, the person who asked for it, its status, and the person who confirmed or rejected it.

Your Claude Settings Are the First Check, Not the Only One

Claude asks before it calls a tool, and you can answer Allow always. Keep that answer for the tools that only read. When you choose Allow always for a tool that changes your account, the four changes above still wait for a person in the console.

This rule is for agents: Claude, ChatGPT and the Adgent. A script that calls the AdCrunch REST API with an API key does not wait, because a developer wrote that script on purpose.


Three Rules That Are Stricter Now

  • Only a person approves a Campaign Plan. Before, Claude and the Adgent could draft a Campaign Plan and approve it. Now only a person approves it, in the console.
  • Spend changes wait for a person. Before, the only check on an activate, an archive or a budget increase was the tool prompt of your AI client, and Allow always removed it. Now a person confirms these changes in the console, whatever your client settings are.
  • A schedule extension waits too. A later end time adds days of spend, the same as a budget increase. Now it waits for a person too.

Also in ChatGPT and in the Console

AdCrunch is not only for Claude. In ChatGPT, you add AdCrunch as an app in developer mode: the ChatGPT guide shows how. In the AdCrunch console, the Adgent uses the same tools, with the same rules.

Ready to connect AdCrunch to Claude?

Open AdCrunch in the Claude directory

No AdCrunch account yet? Start the 7-day trial. Card required, nothing charged for 7 days, cancel anytime.

Read the guide: Connect Claude →