Meta's official connector plugs Claude straight into your ad account, and it's genuine. It also requests write access to your campaigns, your product catalogues and your Business Manager. This is the full members guide: the permissions, the verification, the setup, all 16 skills, your first audit session, and the guardrails for live spend.
Yes. Meta launched these AI connectors publicly, and this guide shows you how to confirm the endpoint is genuinely theirs.
The connector is authentic. The real question is authority: it holds write scopes, so how you run it is what matters.
No. Setup is entirely in Claude's settings UI. You log in with your Meta Business account.
The Meta Ads MCP connector is an official Meta integration that lets an AI assistant (Claude, ChatGPT and others) work directly with a Meta ad account in plain language. MCP stands for Model Context Protocol, the open standard for connecting AI assistants to external tools and data. There are two separate pieces here, and mixing them up is where the confusion starts.
They're independent. Neither needs the other. You can connect the connector and use it with no skills at all. The skills just make Claude far better at the analysis once the pipe is open.
The endpoint was probed without credentials. It returned an OAuth challenge naming the scopes it requires. Here's the raw string, exactly as the server returns it.
ads_management ads_read catalog_management business_management
pages_show_list instagram_basic ads_mcp_management| Scope | What it allows | Access |
|---|---|---|
ads_read | Read campaign, ad set and ad performance data | Read |
ads_management | Create, edit and pause campaigns, ad sets, ads and budgets | Write |
catalog_management | Modify product catalogues and feeds | Write |
business_management | Access and modify Business Manager assets and permissions | Write |
pages_show_list | List the Pages the account can access | Read |
instagram_basic | Basic Instagram account information | Read |
ads_mcp_management | Manage the MCP connection itself | Session |
ads_read alone is enough. That's incorrect. The server's own response above is the proof.mcp.facebook.com resolves through star.c10r.facebook.com to Meta's own edge network. Only Meta can serve on a facebook.com subdomain.Learn the habit, not just this answer: a lookalike domain is exactly how something like this gets spoofed. Before authorising any connector against a money account, confirm the domain belongs to who it claims.
https://mcp.facebook.com/adsLeave OAuth Client ID and Secret empty unless your organisation specifically requires them.
Complete the authorisation with your Meta Business account.
Check the built-in list first. Depending on rollout, the Meta connector may already appear in Claude's built-in connector list. On plans: custom connectors are available on all Claude plans including free, but free accounts are limited to one custom connector at a time; Pro and Max have no limit. Verify this is still current in Claude's settings.
The skills live in a public, MIT-licensed repo that's actively maintained, and it covers Meta plus 11 other ad platforms (Google, YouTube, LinkedIn, TikTok, Microsoft, Apple, Amazon, Reddit, Pinterest, Snapchat and X). Installation instructions live in the repo's README, follow those since they stay current with the code.
https://github.com/AgriciDaniel/claude-adsWhy the source, not a file: pulling from the repo gets you updates, an accountable maintainer, and the ability to read the code before running it. A zip passed around in DMs gives you none of that. You'll see this circulating on Instagram; wherever you saw it, it traces back to this one repo.
Dependency note: meta-generate and meta-photoshoot need a separate image-generation package (banana-claude) installed and configured. The other 14 work without it.
Agents are specialists the audit runs at the same time, so a full account audit completes as concurrent passes rather than one slow sequential crawl.
meta-audit-core · meta-audit-creative · meta-audit-tracking · meta-audit-budget · meta-audit-compliancemeta-creative-strategist · meta-visual-designer · meta-copy-writer · meta-format-adapterDon't start by letting it touch anything. Start by making it prove it can read your account accurately. This keeps the whole first week read-only in practice while you learn what it's good at.
Plain reads only. Check its numbers against Ads Manager before you trust anything else.
Using the Meta Ads connector, list my ad accounts, then show my active campaigns with spend, results and cost per result for the last 7 days. Read only. Do not change anything.130+ weighted checks, four-pillar scoring, a written document of findings.
Run meta-analyze on my account. Produce a written audit document: findings ranked by estimated impact, the evidence behind each finding, and a prioritised fix list. Analysis and recommendations only. Make no changes to the account.There's a specialist for whatever the audit surfaces: meta-capi for tracking, meta-creative for fatigue, meta-budget for spend, meta-landing for the post-click side.
meta-competitor reads the public Meta Ad Library, not your account, so it's genuinely low-risk second-session territory.
AI findings need human review. Spot-check against Ads Manager, and treat the audit as a ranked list of things to investigate.
The division of labour: the connector reads and drafts, you approve. The reporting retainer is the first thing this eats, and the job becomes review and approve. The human still owns every decision.
| Term | Plain English |
|---|---|
| CBO vs ABO | Whether Meta spreads budget across ad sets automatically (campaign budget) or you set each ad set's budget yourself. |
| Pixel / CAPI | Browser-side vs server-side conversion tracking. CAPI survives browser privacy blocking better. |
| Event Match Quality | Meta's score for how well your conversion events match back to real people. |
| Event deduplication | An event_id tells Meta a Pixel event and a CAPI event are the same conversion, so it isn't counted twice. |
| Attribution window | How long after a click or view a conversion still counts, e.g. 7-day click / 1-day view. |
| AEM / SKAdNetwork | The measurement frameworks for iOS traffic under Apple's privacy rules. |
| Creative fatigue | The same audience seeing the same ad too often; rising frequency, falling results. |
| ROAS / MER | Return on ad spend per campaign, vs marketing efficiency for the whole business. |
Settings, Connectors, remove Meta Ads. This stops Claude initiating anything.
Business settings, connected apps, revoke. This kills the access itself. Do both, removing it only in Claude leaves the grant alive on Meta's side.
Check the connected apps list again after revoking.
banana-claude).The connector is Meta's. The skills are third-party, MIT licensed, by AgriciDaniel. Two separate things.
The connector is. Claude plan limits apply to custom connectors: free accounts get one at a time, Pro and Max have no limit.
Yes, it holds write scopes. That's why the permissions section exists and why you confirm every write.
No. Setup is entirely in Claude's settings UI.
Get sign-off first, and authorise a scoped profile.
Remove it in Claude's Connectors settings and revoke the app in Meta Business settings. Both.
No. The connector is an MCP integration AI assistants including Claude and ChatGPT can work with. This guide covers the Claude setup.
Drop your questions in the community chat once you've connected it. Everything else we build in the Lab plugs into the same system.