Hey, it's Cindy 🌱 Here's how to connect your Meta Ads account to Claude (via MCP or CLI) so you can pull reports and manage campaigns without clicking around in Ads Manager.
the basics
Using either MCP or CLI
Meta now has an official way to connect your ad account to AI tools like Claude using Ads AI Connectors.
That means you can pull performance, manage campaigns, adjust budgets, and work with catalogs without manually clicking around inside Ads Manager.
There are two ways to do it:
MCP route
Best if you want Claude to talk to Meta Ads in a more direct, tool-based way.
CLI route
Best if you want a more controlled setup using the official Ads CLI and Claude Code in your terminal.
what you get
What this can do
Once set up, you can use Claude to:
- Pull ad performance reports and insights.
- Create and manage campaigns, ad sets, and ads.
- Update budgets and other campaign settings.
- Manage catalogs and other Meta ad assets.
before you start
What you need first
Before you start, make sure you have:
- A Meta Business Manager account with access to the ad account you want to use.
- A Meta developer app, usually a Business app, if you're setting up API access manually.
- A system user in Business Manager for secure access token generation.
- Access to Claude / Claude Code, depending on which route you choose.
route one
Route 1: MCP
When to use MCP
Use the MCP route if you want the cleanest AI experience: Claude sends structured requests to a Meta Ads tool layer, and that layer handles the actual API work.
This is the best option if you want the least amount of manual terminal work once the connector is set up.
How it works
- Meta's Ads AI Connectors use Meta-authenticated access.
- The connector talks to Meta's Ads MCP server behind the scenes.
- Claude can then query or act on your ad account through that tool connection.
Setup steps
- Create or confirm your Meta Business setup. Make sure the ad account is inside a Business Manager you control.
- Create a system user. Go to Business Settings → Users → System Users and create a new system user for this integration.
- Assign assets. Give that system user access to the ad account you want Claude to use.
- Generate a system user access token. Generate a token for the system user and select the permissions needed for ads access.
- Connect your AI tool. Use the token to authenticate the Meta Ads connector inside your AI setup.
- Test it. Start with read-only prompts like:
- "Show me performance for the last 7 days."
- "List active campaigns."
- "Break down spend by campaign."
route two
Route 2: CLI
When to use CLI
Use the CLI route if you want more control, easier debugging, or a setup that works nicely with Claude Code in your terminal.
This is also the better route if you want to inspect commands before anything gets applied to a live account.
How it works
- You install Meta's official Ads CLI.
- You authenticate it using a system user access token.
- Claude helps you write or run the commands from terminal.
Setup steps
- Set up Meta Business access. Make sure your ad account is available in Business Manager and you have admin or sufficient access.
- Create a system user. Go to Business Settings → Users → System Users and create a dedicated system user for the CLI.
- Assign the ad account. Give that system user access to the specific ad account you want to manage.
- Generate your token. Create a system user access token with the correct ad permissions.
- Install Ads CLI. Follow Meta's official Ads CLI setup docs and install the CLI on your machine.
- Authenticate. Add the token to the CLI using the method in the setup guide.
- Run a test command. Start with a simple read command like:
- list ad accounts
- list campaigns
- fetch insights for the last 7 days
- Use Claude as your operator. Once the CLI works, ask Claude to help you draft commands like:
- "Pull a performance summary for all active campaigns."
- "Generate a budget shift plan based on last 7 days of results."
- "Draft the commands to pause low-performing ad sets."
MCP vs CLI
| Option |
Best for |
Pros |
Cons |
| MCP |
Fully AI-driven workflow |
Most natural Claude experience, less manual work |
More abstract, harder to debug |
| CLI |
Power users and operators |
Clear control, easy to audit, easier to troubleshoot |
More terminal work |
the sticky part
Token setup
This is the part most people get stuck on.
Meta's docs point you toward a system user access token, which is the right choice for automation and server-to-server use.
This is better than using your personal login because it's easier to scope, revoke, and keep separate from your everyday Meta account.
Token checklist
Use a system user, not your personal Facebook login.
Assign only the ad account you need.
Give only the permissions required for what you want Claude to do.
Store the token securely and do not paste it into public places.
keep it safe
Recommended safe workflow
For anything that can spend money, use this flow:
- Claude suggests the action.
- You review the change.
- You approve the command or API action.
- The tool applies it.
This is especially important for budget changes, campaign launches, and pauses.
what to watch
Common issues
"I can't see my ad account" Usually means the system user is not assigned to the ad account correctly.
"Token doesn't work" Usually means the token was generated for the wrong app, the wrong user, or the wrong permissions.
"Claude can read but not write" You likely have read-only permissions instead of management permissions.
"Setup looks different from the guide" Meta changes the UI often, but the core structure stays the same: Business Manager, system user, token, permissions, then connector or CLI.