How to Connect Meta (Facebook) Ads to Claude (Every Option, September 2026)

Which option should you pick

Our pick for most people is PaidSync. Pick something else if one of the narrower cases after it fits you better. The facts behind each pick are in the sections and tables below, with links to each option's own pages.

• PaidSync, our pick for most people. We pick it because setup is Connect in Claude's connector directory and a PaidSync login or Continue with Google, and it needs no API key. It gives Claude 34 Meta Ads write tools, out of 83 in all. It creates campaigns, ad sets and ads, image, video and carousel creatives, Dynamic Creative ad sets, lead forms, and custom, lookalike and engagement audiences, and in Claude it can download the leads from your lead forms. It works across Business Manager ad accounts, and agencies can connect a Meta System User token through the Meta Ads (Agency) option, which PaidSync stores encrypted. The same PaidSync login creates campaigns in Google Ads and LinkedIn Ads too, which Meta's server does not cover and Windsor.ai's LinkedIn actions do not yet include. If Meta is your only channel, PaidSync still installs from Claude's connector directory and publishes its price, where Meta's server is an open beta that is rolling out gradually and goes in as a custom connector by URL. By default, new campaigns and ads start paused or as drafts, and budget edits run as a preview first. Live pauses, enables and removals need an explicit confirmation flag, and a Google Ads campaign budget move of more than 50% needs a second one. Free for 15 tasks a month with no credit card, then priced by usage, from $99 a month for 600 tasks. What to know. PaidSync does not manage Meta catalogs, A/B tests or conversion lift studies, which Meta's own server does. The Free plan stops at 15 tasks a month.

Pick something else if one of these narrower cases fits you better.

• You run only Meta and need Meta's own extras, such as catalogs, A/B tests, lift studies or Business Suite rules. Pick Meta's official ads MCP server. Meta hosts it and states no price for it, and its tool pages list more than 80 tools across seven categories, including catalog management, A/B tests and conversion lift studies, which PaidSync does not manage on Meta. In Meta Business Suite you can block actions such as creating campaigns or editing budgets, and block budgets above an amount you set. It is in open beta and rolling out gradually, and on Claude's Free plan it uses your one custom connector.
• Your main job is joining Meta Ads data with your CRM, your store or many other data sources. Pick Windsor.ai or Supermetrics. Both are Verified in Claude's directory and built to join ads data with other sources. Supermetrics lists more than 170 data sources, and Windsor's Meta page covers cross-channel questions. Both say Claude can create, pause and change budgets on Meta through them.
• You only need reports and want nothing that can change the account. Pick Coupler.io. It is Verified, says it is "read-only by design", and has a free plan for one account with manual refresh, and Coupler's pricing page lists Claude among that plan's AI integrations.
• You are a developer building your own agent. Use Meta's Ads CLI or connect your own Meta app to Meta's server. Both are Meta's own, and the CLI creates everything paused by default.

Every way to connect Meta Ads to Claude

Checked on 27 September 2026 against Meta's own documentation and each vendor's own pages. We did not sign up for the third-party connectors, so what they can do is what their makers say. Meta Ads here means the ads you run on Facebook and Instagram from a Meta ad account. Anthropic has not built a Meta Ads connector of its own, so every route below adds one: Meta's server, a connector from Claude's directory, an automation tool, or your own code.

Meta's official ads MCP server

Meta announced its ads AI connectors, an ads MCP server and an ads CLI, in open beta on 29 April 2026. On 16 July 2026 it opened the server to any developer's own Meta app and added rules that govern what AI agents may do. Meta hosts the server at https://mcp.facebook.com/ads and says it needs "no developer credentials, API setup, or coding". Its Help Center lists Claude, Claude Code, ChatGPT and Perplexity as supported agents, all on that one URL.

Adding it to Claude. Meta's server is not in Claude's connector directory, so it goes in as a custom connector. In Claude, open Customize, then Connectors, click +, choose Add custom connector and paste the URL. Meta says "Owning a Meta app is not a prerequisite." Claude Code adds it as a remote HTTP server, and Meta's developer docs give the exact command for teams that use their own Meta app. Claude's Free plan allows one custom connector, so there Meta's server takes that one slot.

What it can do. As of 27 September 2026, Meta's tool pages list more than 80 tools across seven categories, not the 29 that many guides still quote from launch. The categories are reporting, ad creation and management, catalogs, signals and datasets, help and troubleshooting, A/B tests and conversion lift studies, and activity logs. It reads spend, impressions, CTR, CPC, CPM and conversions with breakdowns and date ranges, plus Meta's opportunity score, anomaly signals, benchmarks, delivery errors and public Ad Library search. It can create campaigns, ad sets, ads and creatives, update or activate them, boost Instagram posts, and manage custom audiences, catalogs, pixel event rules, A/B tests and lift studies.

Safety and control. Meta's tool documentation says "Write tools create entities in a paused state; your AI client asks for confirmation before activation." In Claude, whether it asks depends on your tool approval setting. In Meta Business Suite, under Settings, then Integrations, then Ads MCP server, you pick an ad account or catalog and allow or block actions such as creating campaigns or editing budgets. You can also block budgets above an amount you set. Rules a partner sets on a shared account apply only to that partner's own employees.

What to know before you rely on it. Access is rolling out gradually, and Meta's Help Center says "You may not have access to all tools/features yet". Meta's own pages differ on creatives. The Help Center lists single image, single video, carousel and Advantage+ catalog carousel, while the developer tool list shows a single-image link ad creative. Agencies that connect their own Meta app to manage other businesses' accounts must submit the app for review and request Advanced Access on ads_mcp_management.

Cost and fit. Meta states no price on the pages we checked, which include its announcement, its Help Center and its developer docs. It fits advertisers who run only Meta and want Meta's own tools and controls, such as the opportunity score, benchmarks, lift studies and the rules you set in Business Suite. The official Meta Ads MCP guide walks through it, and PaidSync vs Meta MCP compares the two in more depth.

Third-party connectors in Claude's directory

Every Meta Ads listing in Claude's directory comes from a third party and carries one of two labels. The label in brackets is the one Claude's directory shows. Anthropic tests Verified connectors for quality and compatibility and screens Community connectors before listing them (Anthropic's explanation).

PaidSync.ai is a Community listing. These are the Meta Ads connectors whose abilities and prices we could confirm on each vendor's own page on 27 September 2026. Where a vendor shows both, the monthly price comes first, then the price billed yearly.

• PaidSync.ai (Community). Our pick for most people. Reads, changes and creates campaigns, ad sets, ads and audiences, with budget edits previewed first by default. What it can and cannot do is set out below. Free for 15 tasks a month with no credit card, then priced by usage, from $99 a month for 600 tasks (pricing).
• Windsor.ai (Verified). The directory lists its read tools, and Windsor's own page says Claude can also create campaigns, ad sets and ads, update them, pause and enable them, set campaign and ad set budgets, boost posts and create ad videos. It cannot design new creatives. A 30-day trial becomes a free plan for 1 user, 1 source and 1 account, reading only the past 30 days of data, and Basic is $23 a month, or $19 a month billed yearly (pricing).
• Supermetrics (Verified). Its Meta page says Claude can create Advantage+ or manual campaigns, pause underperformers, adjust budgets, refine targeting and duplicate campaigns, with actions logged in Campaign History, and Supermetrics says every campaign Claude creates starts paused (announcement). Its MCP product page mentions only data queries. No free plan and a 14-day trial, then Starter at €49 a month, or €39 a month billed yearly, for 3 sources and one destination such as Claude (pricing).
• Adspirer (Verified on claude.com, while Adspirer's own docs call it a Community connector). New campaigns are always created paused, and budget, bid or status changes happen only when you ask. Free plan with 15 tasks a month, then Plus at $49 a month, or $40 a month billed yearly (pricing).
• AdWhispr (Verified). Competitor research from public Meta and TikTok ad libraries, plus launching image, carousel and video ads on Meta, all created paused, with pause, resume and budget changes. Free plan with 15 agent calls a month; launching on Meta starts on Pro at $39 a month (pricing).
• Markifact (Community). Says it creates campaigns, ad sets, ads and creatives, manages custom, lookalike and engagement audiences, and shifts budgets with approval-based actions. 200 one-time credits at sign-up, then $79 a month, with 2 months free on yearly billing (pricing).
• AdKit (Community). Draft first. Changes such as pausing ads, shifting budget or duplicating winners wait in AdKit's dashboard until you click approve. A 7-day trial and no free plan, and its FAQ says the $29 plan covers one project (pricing).
• Ryze AI (Community). Ryze's page lists 12 tools for Meta Ads, 9 that read and 3 write tools that wait for approval, and says Claude can pause or enable ad sets, adjust budgets and upload creative. Connecting is free, and its Paid Ads Autopilot is $89 a month.
• Pipeboard (not in Claude's directory, so it goes in as a custom connector). Says it has 30+ tools, audience targeting and bulk budget and status updates, and creates campaigns paused by default. Free plan with 30 tool runs a week and 2 ad accounts, then Pro at $29.90 a month (pricing).
• Coupler.io (Verified, two listings). "Read-only by design", with no campaign creation or budget changes. Free plan for one account with manual refresh, which Coupler's pricing page says includes its Claude integration, then Starter at $32 a month, or $24 a month billed yearly (pricing).
• Adzviser (Community). Adzviser says Claude "cannot create, edit, pause, or change campaigns, budgets, ad sets, or ads" through it. A 14-day trial for $0.99, then Starter at $59.99 a month, or $48.99 a month billed yearly (pricing).
• Porter Metrics (Community). Its Claude connector page says read-only with no write scopes requested from Meta, while its tutorial describes managing campaigns. A free-forever plan includes the connector, then $15 per ad account a month, or $12.50 billed yearly (pricing).

Claude's directory also lists Meta Ads connectors from Madgicx, Whatagraph, Funnel, Polar Analytics, Metricool and others that we did not check in depth.

Automation routes with Zapier and Make

Zapier and Make are both Verified in Claude's directory. They connect Claude to automations rather than to Meta's whole ads API.

Zapier. Its Meta actions cover Facebook Custom Audiences (create an audience, add or remove an email), Facebook Lead Ads and Facebook Conversions. We found no Zapier app for Facebook Ads reporting or campaigns. Each tool call from Claude uses 2 Zapier tasks, and the free plan has 100 tasks a month (pricing).

Make. Claude runs scenarios you build in Make first. Its Facebook Ads Campaign Management app can list, watch and update campaigns, ad sets and ads, with no module that creates a campaign. Make has a free plan with up to 1,000 credits a month, and Core is $10.59 a month, or $9 a month billed yearly (pricing).

Build your own on Meta's tools

• Meta Ads CLI. Meta's official command-line tool, installed with pip install meta-ads. It needs Python 3.12 or later and a system user access token, covers campaigns, ad sets, ads, creatives, insights, catalogs and datasets, and creates everything paused by default. Agents such as Claude Code can run it (Meta's setup guide).
• Your own Meta app on Meta's server. Add the "Create & manage ads with ads MCP server" use case to your app, then authenticate with Facebook Login for Business or a user access token.
• The Marketing API directly. For your own ad account, standard access (Meta now calls it Limited access) to ads_read and ads_management is enough. Managing other people's accounts needs advanced access (now Full access), which requires 500 or more Marketing API calls in 15 days with an error rate below 15%, and business verification applies if your app reads sensitive data (Meta's access rules). Meta lets an ad set budget change 4 times an hour and an account spending limit 10 times a day (rate limits).

How the options compare

What each option can do on Meta Ads from Claude, according to its own pages. Where a vendor shows both, prices are given monthly, then billed yearly, so they compare like for like.

PaidSync, Meta's server, Windsor.ai and Supermetrics side by side

Meta's server is the official route, and Windsor.ai and Supermetrics are the Verified connectors in Claude's directory that say they create Meta campaigns. Here is PaidSync next to them, on the same questions. PaidSync's facts come from its tools and its pricing page; theirs come from their own pages.

How to connect Meta Ads to Claude with PaidSync

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.

How do I connect Meta Ads to Claude on the web?

In 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.

Does it work in the Claude desktop app?

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.

How do I connect Meta Ads to Claude Code?

Run one command in your terminal, then type /mcp inside a session, pick paidsync and sign in with your PaidSync login:

If 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.

Can Claude Cowork use Meta Ads through PaidSync?

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.

Ten Meta Ads prompts to try in Claude

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.

1. "Show me my Meta campaigns from the last 7 days with spend and ROAS." Runs get_fb_performance.
2. "Break down last month's Meta results by placement and by device, and tell me where cost per result is highest." Runs get_fb_performance_by_placement and get_fb_performance_by_device.
3. "Which Meta ads have a frequency above 3 and a lower click-through rate than in the previous 14 days?" Claude runs get_fb_ad_performance for both date ranges and compares them, with get_fb_performance_by_time for the daily trend.
4. "Am I on track to spend my monthly Meta budget? Name the campaigns running over or under." Runs get_fb_budget_pacing.
5. "Is my Meta pixel firing? Show me the events it has received." Runs get_fb_pixel_events.
6. "List my Meta lead forms, then download the latest leads from my main form." Runs list_fb_lead_forms and get_fb_leads. Leads contain personal data, and PaidSync offers lead downloads in Claude, not in ChatGPT.
7. "Search the Meta Ad Library for ads from [competitor] and summarize the offers they run." Runs search_ad_library.
8. "Preview raising the daily budget of my best Meta campaign by 20 percent. Do not apply it yet." Runs update_fb_campaign, or update_fb_adset when the budget sits on the ad set. Both preview by default.
9. "Preview pausing every ad set that spent more than $20 per lead this month. Do not apply it yet." Runs get_fb_adset_performance, then pause_fb_adset as a preview.
10. "Compare spend, CPA and ROAS for Meta, Google Ads and LinkedIn over the last 30 days." Runs get_cross_platform_performance, which reads PaidSync's daily data and totals each currency separately.

What PaidSync can and cannot do on Meta Ads

PaidSync gives Claude 83 Meta Ads tools, and 34 of them can make changes in your account. They are part of 630+ tools across 14 connected platforms.

• Read. Campaign (with ROAS), ad set and ad performance, broken down by placement, device, age and gender, or country, as daily or monthly trends. Budget pacing, pixel events, custom conversions, delivery issues, ad previews and Ad Library search.
• Change. Name, budget, status, targeting, bidding and placements on campaigns, ad sets and ads. Pause or enable at all three levels. Budget schedules, ad set schedules, account controls and pixel configuration.
• Create. Campaigns, ad sets and ads, all paused by default. Image, video and carousel creatives, Dynamic Creative ad sets, duplicates, lead forms and automated rules.
• Audiences. Rule-based custom audiences, lookalikes from an existing custom audience, and engagement audiences from your Page, Instagram, lead forms or videos, plus interest and behavior search for ad set targeting. In Claude, PaidSync can also upload a customer list to a custom audience and download leads from your lead forms.
• Delete. Campaigns, ad sets, ads and audiences.

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 is a verified Meta Business Partner. That means the API connection uses official Meta Marketing API access with approved permission scopes.

Who approves a change before it runs

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 one-tap undo 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.

Turn it into a weekly Meta Ads routine

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.

Frequently asked questions