How to connect Claude to Meta Ads without losing control

Short answer: to connect Claude to Meta Ads, add Meta's hosted server https://mcp.facebook.com/ads as a custom connector in Claude (Customize, then Connectors, then Add custom connector), sign in with Facebook, and approve access to your ad accounts. The connector works for Facebook ads and Instagram ads alike, because both run through the same Meta ad account.

The setup takes a few minutes. The harder part is what comes after: this connector can create campaigns, edit budgets and switch ads on. Most of this guide covers the limits: what to let Claude change, how approvals work, and how to check what it did.

What is the Meta Ads MCP server?

It is Meta's own connector for AI assistants. Meta calls it the ads MCP server: a Meta-hosted Model Context Protocol server that "lets you manage Meta ads directly from an AI agent" (Meta for Developers, updated Jul 14, 2026). Meta announced its ads AI connectors in open beta on April 29, 2026 (Meta for Business, 2026).

What can Claude read and change through it?

Meta groups the tools into seven categories. Three of them can change your account, and the last column marks them.

Source: Meta's tool pages for each category (Meta for Developers, 2026). Third-party guides quote a fixed tool count. Meta's docs do not give one, so ask Claude to list the tools it sees after you connect.

Is it different from the older community servers?

Yes. Community-built Meta Ads servers on GitHub run on your own machine with your own token. Meta's server is hosted by Meta, so there is nothing to install, and Meta itself names Claude Desktop and Claude Code among the clients it has validated (Meta for Developers, 2026).

How do you connect Claude to Meta Ads?

Pick the path by the app you use. The server URL is the same in all of them.

The claude.ai steps come from Anthropic's guide to custom connectors (Anthropic Help Center, 2026). Free Claude accounts can add custom connectors, but only one, so on a free plan this one takes the slot.

Which permissions does Meta ask for?

At a minimum, Meta asks for ads_mcp_management plus ads_read or ads_management (Meta for Developers, updated Sep 4, 2026). That "or" is your first guardrail. ads_read lets Claude look. ads_management lets it change things. Extra permissions such as catalog_management and business_management open more tools, and you do not need them to start.

How do you check that it worked?

Open a new chat, turn on the Meta Ads connector under + and Connectors, and type "List my ad accounts." Meta suggests that same prompt as the first test. If Claude returns names, currencies and time zones, you are connected. If it returns nothing, check that your Facebook login has a role on the ad account; the connector only sees what your login sees.

What should you let Claude change in your ad account?

Start read-only, and widen access one action at a time. A week of reports tells you how Claude reads your account before it touches a budget.

Meta's own advice points the same way: "Keep an app at the Read scope unless an agent needs to make changes" (Meta for Developers, 2026). You set that scope per app, Read or Manage, in Facebook under Settings, then Business Integrations, and you can revoke it there at any time.

Why are new campaigns paused?

Meta builds a brake into the write tools. Its docs say "Write tools create entities in a paused state; your AI client asks for confirmation before activation." Creating a campaign, ad set or ad leaves it paused. Only one tool, ads_activate_entity, switches it on, and Meta's description of that tool ends with "starts spending budget" (Meta for Developers, 2026).

So the pause is the safe default, and the activation prompt is the one to read slowly. Watch ads_update_entity too. It edits fields on a campaign, ad set or ad that is already running, and a budget edit there spends money without any activation step.

Which Claude settings act as approvals?

Claude asks before it calls a connector tool, and you choose how much to trust it. Anthropic's advice is to "only click 'Allow always' when using a server and tool that you trust to run unsupervised." In the Search and tools menu you can switch off individual tools you never want called. And in Research mode Claude can call connector tools without asking, so Anthropic tells you to disable tools that write before you use it (Anthropic Help Center, 2026).

A sensible setup for a small account: "Allow always" for reporting and activity logs, ask every time for create and update tools, and off for ads_activate_entity until week 3.

What are ads MCP server rules?

Rules are Meta's hard limit, enforced on Meta's side no matter what you click in Claude. Meta added them on July 16, 2026, for "anyone with full control of a business portfolio" (Meta for Business, 2026). A rule denies one agent action on one ad account or catalog. You find them on the ads MCP server page in Meta Business Suite settings.

Source: Meta for Developers, Rules best practices (2026). Meta says rules are in limited availability, so your business may not see the page yet. If it does, a 20% budget cap plus edit_status is a good first pair: Claude can draft and suggest, and a person still switches ads on.

How do you read the activity log?

Ask for it every Monday. The tool ads_account_get_activity_logs returns the account's change history and filters it by object, time window, event category or user (Meta for Developers, 2026). A prompt that works: "Show every change to budgets, status and targeting in the last 7 days, who made it, and the value before and after." If a change shows up that nobody in the team remembers, revoke the scope first and ask questions second.

Meta also warns that hidden instructions in a document or web page an agent reads can push it to misuse its access, and advises against giving write scopes to an agent that processes untrusted input (Meta for Developers, 2026). Keep the chat where Claude edits your ads apart from the chat where it browses the web.

What should you ask Claude about your ads once it can read them?

Ask about creatives, because that is where Ads Manager is slowest to answer. The reporting tool returns CTR, CPC, CPM and conversions per ad, and a trend tool tracks CPC, CPM, cost per result, ROAS, CTR and conversion rate over time (Meta for Developers, 2026).

Try on my brand

Which ads are wearing out?

Fatigue shows up as a falling CTR and a rising CPM on the same creative, week over week. Ask: "For every active ad with more than $200 spend in the last 28 days, compare CTR and CPM in the first 14 days with the last 14 days. List the ones where CTR fell by more than 20%." Ask Claude to add frequency if the field list (ads_get_field_context) shows it. A creative that loses a fifth of its CTR in two weeks is a candidate for a refresh, which we cover on creative tracking.

Which creative wins inside the same ad set?

Two ads in one ad set share an audience and a budget, so the comparison is fair. Ask: "In each ad set, rank the ads by cost per purchase and by CTR, and flag any ad set where the top ad by CTR is not the top ad by cost per purchase." The flag shows two cases: a thumb-stopping picture that does not sell points to the offer or the landing page, and a quiet picture that sells is worth a second version.

Try on my brand

Is the account making money?

Ask for spend and purchase value by campaign for the last 30 days, then check the ROAS against your margin. Claude can pull the numbers; whether a 2.5 ROAS is good depends on your costs, which Meta does not know. Put the totals into the calculator:

For the margin math behind a target, see what a good ROAS is.

What are competitors running?

The connector includes ads_library_search, which searches the public Meta Ad Library. Ask: "Find active ads from these three brands and describe the formats they repeat." It answers what others run, not what works for them. Long-running ads are a hint, not proof.

Try on my brand

How Selzee runs next to the Meta Ads connector

Meta's server reads your numbers and edits your campaigns. It does not design ads: its creative tool builds a creative from an image you already have. Selzee fills that gap. It is an AI ad generator that finds the ads winning on Meta right now and recreates them for your brand, with your products, logo, colors and fonts.

Selzee has its own MCP server, so both connectors can sit in one Claude chat. An example flow: Claude reads through Meta's server that your top two ads lost a quarter of their CTR this month, then asks Selzee for new ads with make_ad (a paid-plan tool, about 120 credits per ad, several minutes each), and schedules the one you keep to Instagram or Facebook with schedule_ad. Setup and the full tool list are on the Selzee MCP server page.

The same guardrail logic applies. On Selzee's free plan Claude can read your brand, ads and calendar. Making ads and scheduling posts need a paid plan, and in Claude you set for each tool whether it asks first or stays off. Once a post is live on Instagram, Meta's ads_boost_ig_post can turn it into an ad, and that step spends money, so keep it on "ask every time."

Try on my brand

Connect Claude to Meta Ads: FAQ