Meta ships its own ads MCP server, and it does more than read. Claude can create campaigns, edit budgets, build audiences and pull reporting straight from your ad account. This guide wires it up and hands you the audit prompt we use. Setup takes about 10 minutes.
Verified against Meta's official ads MCP server documentation, August 2026
Most ways of pointing an AI at Meta ads are read only. You ask a question, you get a number back, and then you still go into Ads Manager and click the thing yourself. Meta's own MCP server is different, because the tools it exposes include write access. Claude can make the change, not just describe it.
The server is hosted by Meta at mcp.facebook.com/ads. That matters. Your ad
account credentials are not passing through some third party's servers, which is what happens
with most of the community built Meta ads connectors floating around.
| CATEGORY | WHAT CLAUDE CAN DO |
|---|---|
| Ad creation and management | Create and edit ads, ad sets, and campaigns. |
| Comprehensive reporting | Pull detailed performance reporting to understand how campaigns are doing. |
| Custom audiences | Create, update, and delete custom audiences. |
| Catalog management | Create a catalog, add product data, troubleshoot feed and item visibility issues. |
| Signals and datasets | Check signal health and quality, so you know where your tracking is weak. |
| A/B tests and lift studies | Create and manage A/B tests and conversion lift studies. |
| Activity logs | See account change history, mirroring the Ads Manager campaign history page. |
| Help and troubleshooting | Search Meta Business Help Center articles relevant to what you are stuck on. |
Go to developers.facebook.com and register with the Facebook account that already has access to your ad account. This is free.
In the developer dashboard, create a new app or open an existing one. Then in the left navigation click Use cases, then Add use cases.
In the popup, click Ads and monetization, select Create & manage ads with ads MCP server, and click Save.
This use case is the whole point. Without it, the app exists but the MCP server will not talk to it.
It is on the app dashboard, a long number. You need it for the next command. Meta calls it the App ID, and it is not a secret in the way a token is, but treat it as yours.
This is the command. Run it in your terminal, swapping in your own app ID:
--client-id flag and rename the server. Those are not from Meta.
The line above is the one in Meta's own documentation, flag order and all.
The first time Claude reaches for the server, it sends you to the Facebook Login for Business dialog. Approve it and pick the ad account you want it working on. After that it stays connected.
Open a fresh session and ask for something small and factual:
Real numbers coming back means you are done. Everything past this point is what you can now do with it.
ads_mcp_management permission and submit the app for review. Use cases screen,
Customize on the ads MCP use case, Permissions and features
tab, then Go to app review.
This is the one worth saving. It makes Claude go through the account the way a media buyer would on a Monday morning, and it ends with a score so you can tell whether last week helped.
The morning report. Run it daily and you stop opening Ads Manager to check.
Scaling without breaking learning.
Before you launch anything new.
| WHAT YOU SEE | WHAT TO DO |
|---|---|
| Claude says it has no Meta tools | Start a new session. Connectors are picked up when a conversation begins, not mid chat. |
| The command runs but nothing connects | Check the use case. Create & manage ads with ads MCP server has to be added and saved on the app first. |
| Authorization never appears | Ask it to do something that needs the ad account. Login is triggered on first real use. |
| It connects to the wrong ad account | You picked the wrong one in the Login for Business dialog. Re authorize and choose again. |
| Permission errors on a client account | That is the Advanced Access case. Managing other businesses' data needs App Review. |
The connection above gives Claude the hands. This gives it the checklist. Claude Ads is a free open source skill that turns a vague "audit my account" into a repeatable, scored review, and it covers 12 ad platforms, not just Meta.
Inside Claude Code, install it with the native plugin flow:
Then you get a set of commands. These are the ones you will use most:
| COMMAND | WHAT IT DOES |
|---|---|
/ads setup |
Set up your client, account, KPIs and guardrails once. |
/ads audit meta |
Run a full evidence backed audit of the account and score it. |
/ads monitor |
Check pacing, delivery, tracking, creative fatigue and policy issues. |
/ads optimize --draft |
Draft the changes it recommends, without touching the account. |
/ads report |
Render the run as a clean report you can send to a client. |
--draft until you approve it. So you get the scoring and the
flagging from the audit, and you stay the one who decides what actually ships.
All trademarks belong to their owners. Easy Hive is not affiliated with or endorsed by them. This site is not part of Facebook, Instagram or Meta Platforms, Inc., and is not endorsed by Meta. Savings and results shown are examples, not guarantees; yours will vary. Educational content only, not legal, tax or financial advice. Full disclaimers.