To connect Meta (Facebook and Instagram) Ads to Claude, add PaidSync.ai from Claude's connector directory, sign in, and connect Meta on Facebook's own sign-in screen. No API key or Meta developer app is needed. Claude then gets 92 Meta Ads tools that read results and build or change campaigns, ad sets, ads and audiences, with Meta changes shown as a dry-run preview first. PaidSync.ai is free for 15 tasks a month with no credit card.
Meta runs its own ads MCP server. Meta's developer documentation, checked on 16 October 2026, describes it as "a Meta-hosted Model Context Protocol server that lets you manage Meta ads directly from an AI agent", gives the address https://mcp.facebook.com/ads, and says it "works with any MCP-compatible AI agent". If you only advertise on Meta, start there.
PaidSync.ai fits when Meta is one of several channels. What you can check:
More on the Meta tools: Meta Ads MCP server for Claude and ChatGPT. Running Google Ads too? See how to connect Google Ads to Claude.
Five steps and no API key. Claude signs in to PaidSync, and PaidSync connects to Meta through Meta's own Facebook sign-in. Step 4 is the only part that changes between Claude apps, and the sections after the steps cover each one.
Before you start
Go to paidsync.ai/signup and continue with Google or with an email address. The Free plan is 15 tasks a month with no credit card.
Using Google? You can skip this step. The PaidSync sign-in that opens in step 4 has Continue with Google, and it creates your free account when you press Approve. You then connect Meta from the chat, as step 2 explains. Prefer email? Create the account here first, then click Connect in step 4.
In the PaidSync dashboard, click Connect Meta Ads. Sign in with the Facebook account that manages your ads. The link opens Meta's own consent screen, so PaidSync never sees your Facebook password.
You can also do this from the chat. Once PaidSync is in Claude, ask "Connect my Meta Ads" and open the sign-in link Claude returns.
Running ads for clients? Agencies can connect with a Meta System User token instead, through the Meta Ads (Agency) option in the dashboard. PaidSync stores that token encrypted.
If your Facebook login reaches more than one ad account, tell Claude which one to use, for example "Work on my Acme Store ad account". Claude sets it with set_fb_ad_account. Connecting accounts and picking one uses none of your tasks.
Open PaidSync in the Claude connector directory and click Connect. Or, in claude.ai or the Claude Desktop app, open Customize, then Connectors, click + next to Connectors, search PaidSync, and click Connect.
Sign in with your PaidSync login. That OAuth sign-in is what lets Claude apply changes. Connectors work on every Claude plan, including Free.
Using Claude Code instead? Run claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcp, then type /mcp inside a session to sign in.
On a client with no directory, add PaidSync as a custom connector with the server URL instead (on a Team or Enterprise plan, only an Owner can add one):
https://mcp.paidsync.ai/mcpSave it, then sign in with your PaidSync login when Claude asks.
Ask Claude: "Show me my Meta campaigns from the last 7 days with spend and ROAS"
Claude runs get_fb_performance on your ad account and replies with each campaign's spend and ROAS. Then try the ten prompts further down.
Free for 15 tasks a month with no credit card, then priced by usage, from $99 a month for 600 tasks.
Start Free See a DemoIn claude.ai, open Customize, then Connectors, click + next to Connectors, search PaidSync and click Connect. A PaidSync sign-in window opens. Sign in with your PaidSync login, or pick Continue with Google to create one, and Claude shows PaidSync as connected. Your Meta Ads data is available in the next chat.
This works on every Claude plan, including Free. On a Team or Enterprise plan, an Owner first adds PaidSync for the organization under Organization settings, then Connectors. That step signs nobody in, so each person then connects once with their own PaidSync login.
Connectors belong to your Claude account, not to one device. Once PaidSync is connected on the web, it is also there the next time you open the Claude app on iPhone or Android.
Yes. The Claude desktop app for Mac and Windows uses the same connectors as claude.ai. If you connected PaidSync on the web, open the app and it is already there. If not, follow the same path inside the app: Customize, then Connectors, then search PaidSync.
There is nothing to install and no config file to edit. PaidSync is a remote server at https://mcp.paidsync.ai/mcp that Claude reaches through your Claude account, so it behaves the same on any computer you sign in to.
Run one command in your terminal, then type /mcp inside a session, pick paidsync and sign in with your PaidSync login:
claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcpIf you sign in to Claude Code with your claude.ai subscription, you may not need the command, because connectors you added on claude.ai are available in Claude Code automatically. That does not apply when Claude Code runs on an API key.
The Meta Ads to Claude Code guide goes further, with Meta Ads prompts and the tool behind each one, a headless run with claude -p, and a shared .mcp.json that gives a whole team the same setup. Running more than one ad platform? Connect every ad platform to Claude Code with the same command.
Yes. Cowork is where Claude takes on a multi-step task and works through it for you, and it uses the same connectors as the rest of your Claude account. Once PaidSync is connected, a Cowork task can pull Meta Ads data and act on it. Cowork itself needs a paid Claude plan, unlike connectors, which work on every plan including Free.
A good first task: "Check every active Meta ad set for rising frequency and falling click-through over the last 14 days, and list the ads that need fresh creative." To repeat a task, type /schedule in Cowork, which suits a weekly performance report.
In Manually approve mode, Cowork pauses and asks before it takes an action. Keep that mode for any task that can change a live account: it is the check you control, next to PaidSync's own defaults (new campaigns and ads start paused or as drafts, and live pauses, enables and removals need an explicit confirmation flag). Some Pro and Max accounts show no separate Cowork option. There you describe the task in the normal message box.
Each prompt runs on the PaidSync tools named after it and uses one or more of your tasks. Prompts 8 and 9 ask for a preview only.
get_fb_performance.get_fb_performance_by_placement and get_fb_performance_by_device.get_fb_ad_performance for both date ranges and compares them, with get_fb_performance_by_time for the daily trend.get_fb_budget_pacing.get_fb_pixel_events.list_fb_lead_forms and get_fb_leads. Leads contain personal data, and PaidSync offers lead downloads in Claude, not in ChatGPT.search_ad_library.update_fb_campaign, or update_fb_adset when the budget sits on the ad set. Both preview by default.get_fb_adset_performance, then pause_fb_adset as a preview.get_cross_platform_performance, which reads PaidSync's daily data and totals each currency separately.PaidSync gives Claude 92 Meta Ads tools, and 36 of them can make changes in your account. They are part of 630+ tools across 14 connected platforms.
Limits worth knowing. There is no dedicated creative fatigue tool, so Claude spots fatigue by comparing frequency and click-through per ad across two date ranges. Interests and behaviors are ad set targeting, not saved custom audiences. Automated rules run on their own once created. Image and video uploads apply on the first call, with no preview. Meta's own limits still apply, such as 4 budget changes an hour on one ad set.
PaidSync runs a Meta-approved app. That means the API connection uses official Meta Marketing API access with approved permission scopes.
By default, new campaigns and ads start paused or as drafts, and budget edits run as a preview first.
These are defaults, not locks. Claude can apply a change or create something live when you ask it to. Live pauses, enables and removals need an explicit confirmation flag, and Claude's own per-tool approval setting is a second check you control. Claude lets you set each connector tool to need your approval, and during Research it can run connector tools without further approval, as Anthropic's connector guide explains. Keep approval on for PaidSync's tools that change ads. Approval cards, and Undo on an applied card whose change has a safe inverse, exist only in the PaidSync web workspace. For changes made from Claude, get_operator_change_log returns PaidSync's own change log with an account-level before and after.
PaidSync never sees your Facebook password. It stores the access tokens Meta issues, encrypted with AES-256 in Google Cloud (United States), and deletes them when you disconnect. You can also revoke access from your Meta account settings. The security page lists every control.
When a prompt gives you an answer you want every week, save it instead of retyping it. Ask Claude to save the job as a PaidSync workflow, which it does with paidsync_workflows_save, then run it by name each Monday with paidsync_workflows_run. A good first one joins prompts 3 and 4 above, ad fatigue and budget pacing, into one Monday check. On a paid Claude plan, Cowork can also repeat a task for you with /schedule.
The PaidSync workflow library shows twelve paid media workflows built this way, each with its trigger, the platforms it touches and the point where a person approves. Building your own agent? See how to build your own AI ads agent.
Meta runs its own ads MCP server at https://mcp.facebook.com/ads. Meta's developer documentation, checked on 16 October 2026, says it "works with any MCP-compatible AI agent". PaidSync.ai is a separate connector in Claude's connector directory that covers Meta and 13 more platforms in one connection.
Yes, through PaidSync.ai. Claude can build campaigns, ad sets, ads, creatives and audiences, and change budgets and status. Meta changes run as a dry-run preview by default, and destructive changes need an explicit confirmation.
No. You connect Meta on Facebook's own sign-in screen, and PaidSync.ai never sees your Facebook password. Agencies can also connect a Meta System User token through the Meta Ads (Agency) option.
Yes. If your Facebook login reaches several ad accounts, tell Claude which one to use, and switch at any time. Connecting accounts and picking one uses none of your tasks.
PaidSync.ai is free for 15 tasks a month with no credit card and no time limit. Pro is $99 a month for 600 tasks, or $75 a month billed yearly. Team is $249 a month for 5 seats and 6,000 shared tasks.
Yes. Instagram ads run through Meta's ad accounts, so the same 92 Meta tools read and change them, including placement breakdowns for Facebook and Instagram.
630+ tools. 14 platforms. One connection. Start free.