How to use Claude to manage Meta ads
How to use Claude to manage Meta ads: official connector, read-only first, you approve every write. A founder guide for Australian paid spend.
- PUBLISHED
- READ
- 8 minutes
How to use Claude to manage Meta ads is this: connect Meta’s ads MCP endpoint, let Claude read the account, and keep every create, edit, pause and budget change behind your explicit approval.
I am Adam Stewart. I run Digital Bond. I write for founder-led Australian businesses that want AI to assemble the work, not spend the budget.
This is not how to use Claude for marketing. That guide uses Claude Chat to research and draft a campaign brief. This one involves a paid media account and permissions that can support account changes. Treat Claude like a junior buyer with Ads Manager access until you have watched it work read-only for a fortnight.
Claude Meta ads: the short answer
| Question | Answer |
|---|---|
| Official server URL | https://mcp.facebook.com/ads |
| Best first use | Read-only reporting and analysis |
| Main risk | The requested grant includes write-capable advertising and business scopes |
| Safe default | Every write is described first and waits for your explicit yes |
| Human stays on | Send, publish and spend |
The member walkthrough this article is based on lives in AI Systems Lab. This public guide covers how to verify the endpoint, connect it, run the first read-only session and keep spend human-controlled.
What is Claude Meta ads, in plain English?
Two things get mixed up. Keep them apart.
The connector is the pipe. The server is at https://mcp.facebook.com/ads. Meta’s public OAuth metadata identifies that URL as the protected resource and sends authorisation through Facebook and the Graph API.[1]
The skills are optional instructions. They can structure audits and reporting after the pipe is open. The public claude-ads repository by AgriciDaniel is MIT-licensed, but it is a community project, not a Meta or Anthropic product.[3] You can start with the connector alone.
Claude Meta ads, in practice, is that pipe plus a human who still owns spend.
Is the Meta ads connector official, or a lookalike?
Before you authorise anything against a money account, confirm the domain.
The hostname must be mcp.facebook.com. Meta’s live metadata names https://mcp.facebook.com/ads as the resource and lists the Facebook OAuth flow behind it.[1] A lookalike domain with extra words, a different ending or a misspelling is not the same server.
If a Reel, direct message or ZIP file gives you a different connector URL, stop.
What permissions does Claude request for Meta ads?
At the time of checking on 29 August 2026, Meta’s endpoint advertised these scopes:
ads_management ads_read catalog_management business_management pages_show_list instagram_basic ads_mcp_management.[1]
That is not a read-only grant. The scope set includes permissions used to manage ads, catalogues and business assets. Saying “read only” in a prompt is therefore an operating rule, not a technical restriction on the OAuth grant.
That distinction matters. The endpoint can be legitimate while the level of authority is still too broad for day one.
How do I connect Claude to Meta ads?
For an individual Pro or Max account, Anthropic’s current path is:
- Open Claude and go to Customize > Connectors.
- Click +, then Add custom connector.
- Enter the remote MCP server URL:
https://mcp.facebook.com/ads. - Leave Advanced settings blank unless your organisation has supplied OAuth client credentials.
- Click Add, then connect and authorise the Meta Business account that should see the ads.
For Team and Enterprise plans, an Owner or Primary Owner adds the custom connector in Organization settings > Connectors before members connect their own accounts. Anthropic says remote MCP connectors are available on Free, Pro, Max, Team and Enterprise plans, with Free users limited to one custom connector.[2]
Anthropic also warns that remote connectors can read, create, modify or delete data according to the permissions granted. Review tool approval requests carefully and do not choose an always-allow option for write tools you have not supervised.[2]
If the authorisation flow does not show the Meta assets you expect, check the Facebook profile and Business permissions before assuming the server URL is broken.
What should I do in the first Claude Meta ads session?
Do not let it touch anything. Make it prove it can read.
First prompt
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.
Check those numbers in Ads Manager before you trust a second prompt.
Then ask for analysis only:
Audit this Meta ads account. Rank findings by likely impact, show the evidence behind each finding, and give me a prioritised fix list. Analysis and recommendations only. Make no changes to the account.
Go deeper only on what it flags: tracking, creative fatigue, budget allocation or the landing page. Treat the output as a ranked list of things to investigate. Claude can still be confidently wrong.
What rules should I use if Claude can affect spend?
I use seven standing rules.
- Scoped profile. Authorise a login that reaches only the ad accounts you intend to expose.
- Read-only fortnight. Run audits and reports only for two weeks, and repeat that instruction in every session.
- Caps set by hand. Set campaign and account spending limits inside Ads Manager before any write.
- Everything launches paused. If Claude creates a campaign, ad set or ad, it remains paused until you inspect it.
- Confirm every write. Before any create, edit, pause or delete, Claude must describe the exact change and wait for your explicit yes.
- Review the trail. Check Ads Manager change history and connected apps on a schedule.
- Idle means disconnected. If you are not using the connector, remove it from Claude and revoke the Meta connection.
The division of labour is simple: Claude reads and drafts. You approve. It can compress the first pass, but it does not remove the need for a media buyer’s judgement.
Can I use Claude Meta ads on a client account?
Yes, but the client should know what is being connected before you connect it.
Explain that the endpoint is Meta-controlled, any community skills are separate, and the grant includes scopes that are not read-only. State that you will begin with reporting and analysis, with every account change human-approved.
Use a profile that reaches only that client’s assets. Record when you connected, which profile was used, who approved it and when the connection will be reviewed or revoked. Show the client where the off switch is in their Meta Business settings.
If they will not sign off, do not connect it.
How do I disconnect Claude from Meta ads?
Remove access in both systems:
- In Claude, go to Customize > Connectors, open the connector menu and remove it.[2]
- In Meta Business settings, revoke the relevant connected app or business integration.
- Recheck the Meta connection list to confirm the grant is gone.
Removing the connector from Claude and revoking the Meta-side grant closes both ends of the connection.
What Claude Meta ads will not do
It will not make a weak offer compelling.
It will not make broken conversion tracking trustworthy.
Community skills are not Meta products and are not Anthropic products.[3]
It will not replace a media buyer. It compresses the first pass, not the decision.
And it is not a reason to hand a model your entire Business Manager on day one. Start narrower than you think.
My honest read
The connector endpoint is real. The advertised scope set is the story. Most short demos skip that part.
Connect it to the smallest sensible account surface. Run it read-only. Check its numbers against Ads Manager. Approve every write.
The guardrail is the same one I use everywhere: AI assembles the work. You stay on send, publish and spend.
FAQ
How do I use Claude to manage Meta ads without letting it spend?
Connect the Meta endpoint, then put “read only, do not change anything” in every prompt for a fortnight. Set spending limits in Ads Manager yourself. Keep anything Claude creates paused until you inspect it and choose to launch.
Is Claude for Facebook ads the same as Claude Meta ads?
Yes in normal usage. Facebook and Instagram ads are managed through Meta Ads Manager. The same approval rule applies: Claude can analyse and draft, but you approve the write.
Do I need the GitHub skills to start?
No. The connector works without community skills. Skills can improve the structure of an audit, but you should install them from a repository you have reviewed rather than a ZIP sent in a direct message.
Does saying “read only” remove Meta’s write permissions?
No. It is a session instruction, not a reduced OAuth grant. Meta’s endpoint still advertises management scopes.[1] Use account limits, paused launches and explicit approvals as additional controls.
What if I only want Claude for marketing, not ads?
Stay in Chat and write the brief. Do not add an ads connector. Start with how to use Claude for marketing instead.
What to do this week
If you already run Meta ads, add the endpoint and run the seven-day read-only prompt. Check every number against Ads Manager.
If the numbers match, run one analysis pass. Change nothing.
For the longer setup, permissions table and skill workflow, use the Claude + Meta Ads member guide.
If the constraint is the whole marketing system rather than this week’s ads account, start with the Digital Bond scorecard.