Translated from the Japanese original on mureo.jp.
Meta Ads (Facebook and Instagram) can also be driven by giving Claude Code instructions in plain language. The thinking is no different from Google Ads. But because Meta Ads is a platform where audiences and creative, not keywords, take the lead, both what pays off in automation and what trips you up are a little different. This article looks at how driving Meta Ads from Claude Code fits together, and where you are likely to catch.
The overall picture is in Can you automate ad ops with Claude Code?. The search side is covered in Driving Google Ads from Claude Code and Driving Yahoo! JAPAN Ads from Claude Code, and Amazon Ads in Driving Amazon Ads from Claude Code.
Connecting to Meta Ads through MCP
Claude Code on its own does not hold Meta Ads data. MCP (Model Context Protocol) sits in between and talks to Meta’s Marketing API. That structure is the same as with Google Ads.
What differs is the query convention. Google Ads has GAQL as its own dedicated syntax; with Meta Ads you call Marketing API endpoints, specifying the fields you want and the aggregation conditions. You can pull numbers at each level: campaign, ad set, ad, placement. Assembling those calls is likewise something you do not need to learn; Claude Code handles it.
Hurdles before you are connected
Creating an app and getting access permissions reviewed Using the Meta Ads API requires setting up an app in Meta for Developers and obtaining permission to use the Marketing API. Business verification and permission review can be part of it. It is the equivalent of Google Ads’ developer token, but the review is finer-grained. This may likewise be where people stall on the first attempt.
Access token expiry Meta access tokens expire. Without a mechanism to exchange a short-lived token for a long-lived one, or to refresh before expiry, the connection will one day simply cut out and stop. It is not something you can leave alone, so designing it through to how tokens get refreshed is the safe move.
Understanding the Business Manager structure In Meta Ads, ad accounts, Facebook Pages, Instagram accounts, pixels, and the Conversions API (CAPI) hang under a Business Manager. Mix up which account you are operating on and you will apply changes to a different client. Checking the structure before you connect is safer.
The biggest difference from Google Ads
Google Ads runs on search keywords; Meta Ads runs on audiences and creative. Who you reach, and with which asset. That is what largely determines results, so what pays off when you delegate to Claude Code changes too. Beyond reading numbers, the main uses are monitoring creative fatigue and separating out how delivery performs by placement (Facebook, Instagram, Audience Network). Finding and flagging ads whose frequency has risen while click-through has fallen is the kind of check that fits well.
What you can do with Meta Ads once connected
- Pull data across the account: read numbers by campaign, ad set, ad, and placement from a single instruction, and find CPA and frequency deterioration.
- Automate the check: delegate the daily number check and surface only what needs attention. It also catches fatigued ads and skewed delivery.
- Delegate trafficking and changes: adjusting ad set budgets, swapping creative, and revisiting placements can all be executed from your instructions.
Where people get stuck with Meta Ads
When measurement drifts, the optimization goes with it Meta Ads measures conversions with the pixel on your site and the server-side Conversions API (CAPI). If that measurement is broken, both Meta’s automatic optimization and your evaluation of the numbers that come back go wrong together. Before you connect and start moving numbers, confirm once that measurement is being captured correctly.
Do not touch too much mid-learning-phase Meta ad sets have a learning phase, and large changes made before delivery stabilizes reset the learning and disturb results. Delegating to an AI tempts you to fix every little thing you notice, but on Meta Ads those small frequent changes backfire. Deciding in advance how often and how far you may change things keeps delegation from falling apart.
Record the reason for changes The same as with Google Ads and Yahoo! JAPAN Ads: if there is no log of the changes the AI made, you cannot explain the reasons later. The more platforms you handle, the more the design of your records pays off.
Summary
Connecting Meta Ads to Claude Code is not difficult, provided you can put the tooling together. What Meta Ads asks of you, beyond the connection, is measurement you can trust, a change cadence that accounts for the learning phase, and the question of how much to delegate and what to record. That is explored in Is it safe to hand ad ops to Claude Code?. We build mureo, which productizes multiple platforms including Google Ads, Yahoo! JAPAN Ads, and Meta Ads along with the design for delegation, so you can talk to us not only about how to connect but about how to structure operations.