Your Meta ads.
In Claude. No install.

01 /

Prepare the account you want to inspect

Start with a ZuckerBot account, a Claude account with custom connectors available, and Meta access to the ad account you want to review. You do not need a Facebook Page for the audit itself.

If you have not connected Meta, open Start free, sign in and complete the Meta connection. Use the ZuckerBot identity that owns the business you intend to audit. If you manage multiple businesses, confirm the selected business and ad account in your account before asking for analysis.

The browser audit remains an option if you want the first report before configuring Claude. Claude is an optional way to explore that account, not a prerequisite for running the browser audit.

02 /

Add the hosted connector in Claude

1. Open Claude’s Connectors area, under Customize in the current help documentation. Some interfaces label this Settings → Connectors.
2. Choose Add custom connector and name it ZuckerBot.
3. Enter the remote server URL below, then add the connector.
4. Choose Connect if prompted, sign in to ZuckerBot, and review its OAuth consent screen. This hosted flow does not require you to copy an API key.
5. Enable ZuckerBot for the conversation from Claude’s connector controls.

https://zuckerbot.ai/api/mcp

Claude Team and Enterprise workspaces may require an owner to add the connector first. Menu names and availability can change; use Anthropic’s custom connector instructions for the current controls.

03 /

Verify context before asking for findings

An authenticated connector is not proof that the right Meta account is ready. The ZuckerBot login and Meta connection are separate. Ask Claude which connected business and ad account it can identify; if they do not match your intended account, stop and correct the selection.

Then request the account audit by its tool name, zuckerbot_audit_account. That makes the first action explicit and avoids an open-ended instruction such as “optimise all my ads.”

Use ZuckerBot to run zuckerbot_audit_account on my connected Meta ad account. This is a read-only audit: do not create, edit, pause or launch ads, and do not change budgets or settings.

Identify the account and report date range. State any incomplete data. Summarise the main findings with their evidence and uncertainties. Treat flagged spend as spend to review, not recoverable savings. Give me the saved report link if one was returned, then wait for my next instruction.

ZuckerBot’s hosted endpoint supports OAuth for this connection. That means a sign-in flow, not putting a Meta access token, ZuckerBot key or password into the conversation. Never paste those credentials into a prompt.

04 /

Ask better follow-up questions

Once an audit returns, the useful next step is to challenge its interpretation. Keep questions tied to the returned evidence:

• “Which flagged ads still have an acceptable cost for their actual result type? Explain without changing anything.”
• “Which findings depend on missing data? Separate observations from hypotheses.”
• “For this fatigue flag, explain the comparison periods and what else might account for the CTR decline. Read-only checks only.”
• “Draft a creative test brief from this finding. Do not upload, create or publish anything.”

For the report’s measurement limits, use the Meta ads audit checklist. For a creative decision, work through the fatigue diagnostic guide before turning a flag into a replacement plan.

05 /

Keep analysis and account changes separate

The ZuckerBot connector exposes more than audit tools. A read-only prompt does not convert the entire connection into a read-only permission scope. Review each tool request; where Claude allows tool controls, disable write tools you do not need.

Pausing an ad, launching a campaign, uploading assets or changing a budget are separate actions. A request to explain a report is not approval for any of them. Before a later change, review the exact object, proposed action, budget impact and any required confirmation.

Remote connector traffic originates from Anthropic’s infrastructure. Audit data returned to Claude becomes part of that assistant workflow. Review ZuckerBot’s privacy policy and the privacy settings of the Claude account you use. Custom connector configuration is not an Anthropic certification or endorsement. Anthropic explains the permission considerations.

06 /

Recover without starting over

If the problem remains, contact ZuckerBot support with the step that failed and the visible error. Remove passwords, API keys and access tokens from screenshots. A tool error is not a reason to relax your account’s permissions.