Pull reports and manage campaigns from Claude instead of clicking around in Ads Manager. Two setup routes, both official.
Meta has an official way to connect your ad account to AI tools like Claude, called Ads AI Connectors. Once connected, you can pull performance data, manage campaigns, adjust budgets, and work with catalogs without manually clicking through Ads Manager.
There are two ways to set it up. MCP is the more direct, tool-based route. CLI gives you more control and is easier to audit. Pick based on how hands-on you want to be.
Use MCP 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.
Meta's Ads AI Connectors use Meta-authenticated access. The connector talks to Meta's Ads MCP server behind the scenes, and Claude queries or acts on your ad account through that connection.
Confirm your Business setup. Make sure the ad account is inside a Business Manager you control.
Create a system user. Business Settings → Users → System Users → 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 token. Generate a system user access token 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 read-only. Start with prompts like the ones below before you let Claude write anything.
Use CLI if you want more control, easier debugging, or a setup that works well with Claude Code in your terminal. It's also the better route if you want to inspect commands before anything applies to a live account.
You install Meta's official Ads CLI, authenticate it with a system user access token, and Claude helps you write or run commands from the terminal.
Set up Business access. Make sure your ad account is available in Business Manager with admin or sufficient access.
Create a system user. Business Settings → Users → System Users → create a dedicated system user for the CLI.
Assign the ad account. Give that system user access to the specific account you want to manage.
Generate your token. Create a system user access token with the correct ad permissions.
Install the Ads CLI. Follow Meta's official setup docs and install it on your machine.
Authenticate. Add the token to the CLI using the method in Meta's setup guide.
Run a test command. Try "list ad accounts," "list campaigns," or "fetch insights for the last 7 days."
Use Claude as your operator. Once the CLI works, ask Claude to draft the commands.
| Option | Best for | Pros | Cons |
|---|---|---|---|
| MCP | Fully AI-driven workflow | Most natural Claude experience, least manual work | More abstract, harder to debug |
| CLI | Power users and operators | Clear control, easy to audit, easier to troubleshoot | More terminal work |
This is the part most people get stuck on. Meta's docs point you toward a system user access token, the right choice for automation and server-to-server use. It's easier to scope, revoke, and keep separate from your everyday Meta login.
For anything that can spend money, use this flow, especially for budget changes, campaign launches, and pauses: