Meta Ads MCP Setup for Claude and ChatGPT (And Why It Says False)

Key Takeaways

Meta now ships an official MCP server at https://mcp.facebook.com/ads. It plugs directly into Claude, ChatGPT, Perplexity, and Cursor and is free to use.
Setup takes about five minutes in Claude Pro or Max. ChatGPT requires Developer mode to be turned on first.
The is_ads_mcp_enabled: false flag is the most common issue advertisers are running into right now. It is a phased rollout, not a permission problem on your account.
Fall back to a third-party MCP like Pipeboard, Composio, or Adzviser while you wait for Meta to flip the flag on your account. We did this on a recent client account and lost zero workflow time.
For NZ and Australian businesses, the cost saving alone is significant. Third-party Meta MCPs were charging USD $25 to $99 per month before Meta released its own.
AI cannot delete or pause your campaigns by accident. Meta’s official server defaults to read-only and pauses any new campaigns by default. You still need to verify before approving anything.

Last week I tried to run a quick performance check on the Compton Cowboys ad account through Claude. Simple ask, “How is the campaign performing?” Instead of an answer I got back a quiet little flag, is_ads_mcp_enabled: false, on both ad accounts inside the same business manager.

If you have hit the same wall, you are not alone. Meta’s official Ads MCP server is rolling out unevenly, and right now plenty of legitimate business accounts are showing up as ineligible. This guide walks through what the Meta Ads MCP actually does, how to wire it up in Claude and ChatGPT, why the false flag happens, and what to do while you wait for it to flip.

What is the Meta Ads MCP?

The Meta Ads MCP is an official Model Context Protocol server, hosted by Meta at https://mcp.facebook.com/ads, that lets AI tools like Claude and ChatGPT securely connect to your Facebook and Instagram ad accounts. Once connected, the AI can pull performance data, analyse audiences, summarise campaigns, and (depending on your client) draft new campaign structures, all from a chat window.

Think of it as a USB-C port for your ad account. Before MCP, every AI tool that wanted to read your Meta data needed its own custom integration, its own OAuth flow, and usually a paid middleman. Now there is one shared standard, and Meta has shipped a server that anyone can plug into.

The currently supported AI clients are:

Claude (Pro and Max plans, plus Claude Code)
ChatGPT (with Developer mode enabled)
Perplexity
Cursor

Meta’s release does not kill the third-party MCP market overnight, but it does change the economics. Pipeboard, Composio, Adzviser, and similar services were charging anywhere from USD $25 to $99 a month for the same basic capability. Meta’s official server is free.

What it actually lets the AI do

The MCP exposes a set of tools the AI can call on your behalf. In practice, that breaks down into four categories.

Reporting and analysis. Pull insights at the account, campaign, ad set, or ad level. Compare date ranges. Find the worst spending creatives. This is where most agencies get the immediate win.

Audience research. Inspect saved audiences, custom audiences, lookalikes, and the targeting on each ad set. Surface overlap and waste.

Creative review. Pull ad previews, ad copy, and creative metadata so the AI can spot fatigue, off-brand copy, or compliance risk before you ever scroll a feed.

Campaign management. Create campaigns, ad sets, and creatives. Update budgets. Pause underperforming ads. The official Meta server and most reputable third parties default new campaigns to paused status, which is the right behaviour. You should always review before activating.

What it will not do, and should not do, is run wild. There is no “spend my whole budget on what you think is best” button, and you should be very wary of any tool that markets itself that way.

How to set up the Meta Ads MCP in Claude

This is the five-minute path. You need a Claude Pro or Max plan.

Open Claude in your browser and go to claude.ai/settings/connectors.
Click Add custom connector.
Name it something like “Meta Ads”.
Paste the URL: https://mcp.facebook.com/ads
Choose OAuth as the authentication method.
Click connect. Meta will pop up its standard login and permission screen.
Sign in with the Facebook account that has access to the ad accounts you want to manage.
Approve the requested scopes (read insights, manage ads, etc.).
Back in Claude, run a simple test: “Which ad accounts do I have access to?”

If everything is healthy, Claude will list your ad accounts. If you see is_ads_mcp_enabled: false, skip ahead to the troubleshooting section.

How to set up the Meta Ads MCP in ChatGPT

ChatGPT needs one extra step because custom MCP servers sit behind Developer mode.

In ChatGPT, open Settings.
Go to Apps, then Advanced.
Toggle Developer mode on.
Back in Apps, choose Add custom server (or “Create app”, depending on your plan).
Paste https://mcp.facebook.com/ads as the MCP URL.
Authenticate with Facebook through the OAuth flow.
Save and start a new chat. Test with the same “list my ad accounts” prompt.

ChatGPT’s developer mode is rolling out plan by plan, so if you are on a personal plan and do not see the toggle yet, that is expected. Claude Pro is the more reliable starting point right now.

How to set it up in Claude Code

If you are using Claude Code on the command line, one command does it:

claude mcp add --transport http meta-ads https://mcp.facebook.com/ads

Authenticate when prompted. From there, the Meta Ads tools become available in any Claude Code session.

The is_ads_mcp_enabled false problem

Now to the part that is tripping people up.

When the connection succeeds at the OAuth layer but the AI cannot actually read campaign data, the server returns the flag is_ads_mcp_enabled: false against your ad account. The Reddit threads on r/FacebookAds include several advertisers running into the same wall on legitimate verified business accounts.

What is happening: Meta is doing a phased rollout. The OAuth scopes are live for everyone, but the underlying ad account flag that grants MCP access is being flipped on per account, not per app or per business manager. That is why you can connect one Facebook profile to Claude, see five ad accounts, and find that two of them work and three return false. Bryan Cano’s public testing on X showed exactly this pattern, with adjacent accounts inside the same connector returning different values for the flag.

Likely factors influencing whether your account has been enabled:

Region. US accounts appear to be flipped first. Anecdotal reports from NZ and Australian advertisers suggest a wider regional rollout is queued for the second half of 2026.
Business verification status. Verified businesses appear to be prioritised over personal ad accounts.
Account age and activity. Newer or very low spend accounts seem to be later in the queue.
Spend tier. Some agencies report that their highest spend accounts flipped first within the same business manager.

Meta has not published the exact eligibility criteria, and waiting on support to manually flip the flag is not productive. The tactical answer is to keep using AI in your ad workflow with a third-party MCP while Meta finishes the rollout.

What we did on the Compton Cowboys account

When both ad accounts came back false, we kept the official connector installed (it costs nothing to leave in place) and routed the actual queries through a third-party Meta MCP. The AI workflow ran exactly the same. The only thing that changed was the underlying transport. Total time lost: about ten minutes, mostly spent reading the error response.

The lesson is simple. Do not block your team’s AI workflow on a Meta rollout you do not control. Install the official MCP, keep it ready, and run a backup MCP for the accounts that still show false.

What this means for NZ and Australian businesses

Three things stand out for businesses on this side of the world.

The cost saving is real. Third-party Meta MCP servers like Pipeboard, Composio, and Adzviser were charging between USD $25 and $99 per month per seat. For an NZ agency managing a handful of accounts, that is real money. Meta’s official server costs nothing to use beyond the AI subscription you already have.

There is a first-mover window. AI workflows on Meta data are still novel in the NZ and AU market. Most local agencies are not running them yet, and most local SMBs do not know they exist. If you build a fast morning brief or a weekly performance summary on top of MCP now, you are operating ahead of the curve.

ANZ rollouts usually lag the US. Meta historically ships features to North America first, then Europe, then Asia Pacific. Plan for the official server to be inconsistent on NZ and AU accounts for the next few months and budget that into your workflow design.

If you are running paid ads as part of a wider digital strategy, the paid ads service we run integrates Meta MCP workflows for client reporting and creative diagnostics. We use it daily.

Five workflows we run on Meta MCP

These are the queries we use most often, in order of how much time they save.

Weekly performance summary. “Pull the last seven days of performance for ad account X. Highlight the three best ads by ROAS and the three worst by CPM.”
Creative fatigue scan. “Show me every active ad in this account where frequency is above 3 and CPM has risen more than 20% over the last 14 days.”
Audience overlap check. “List the active ad sets in this campaign and tell me where audiences overlap by interest or geography.”
Budget pacing review. “Are any campaigns pacing more than 15% above or below their daily budget over the last seven days? Group by objective.”
Cross-campaign anomaly detection. “Compare this week’s CTR by placement against the previous four-week average. Flag anything that has shifted more than two standard deviations.”

These queries replace what used to be an hour or two of dashboard clicking every Monday morning. For agency teams managing five or ten clients, that math compounds quickly.

If your reported numbers have looked off since March, the MCP also makes the new Meta March 2026 attribution rebuild much easier to navigate, because you can ask Claude to compare link-click and engage-through windows side by side in seconds.

If you want a deeper read on AI-assisted ad management, our post on three ways to use AI in your Meta ad account covers the broader strategy.

Should you use Meta’s MCP or a third party?

Quick decision framework:

Use Meta’s official MCP when your account has been enabled, when you want zero monthly cost, and when you need basic reporting and analysis.
Use a third party (Pipeboard, Composio, Adzviser) when your account is still flagged false, when you need richer tooling like cross-account analytics, or when you need features Meta has not shipped yet such as catalogue management or full automation.
Use both side by side if you manage multiple accounts in different rollout cohorts. Cost is minimal, and you keep workflow continuity.

For agencies and businesses just starting with AI in their ad workflow, I would not stress too much about the choice. Start with whichever connects today, prove the workflow internally, and switch later when Meta finishes the rollout.

Risk and governance

A few rules we follow internally and pass to clients.

Default to read-only review. When you set up the connector, decline write-style permissions if your AI client offers granular control. You do not need create or edit access to run reporting.

Treat the AI like a junior team member. Verify any change before approving. Even when campaigns default to paused, audience targeting, budgets, and creative copy can drift in unexpected directions if you skip review.

Audit log monthly. Both Meta and the AI client log every action. Skim them once a month to catch anything weird.

Permissions hygiene. When a contractor or agency engagement ends, revoke the MCP authorisation in your Meta business settings, not just inside the AI client.

This is the same governance you would apply to any third-party tool with write access to your ad account. The novelty of AI does not change the fundamentals.

Frequently asked questions

What does is_ads_mcp_enabled: false mean? It means your specific ad account has not been switched on for Meta’s MCP server yet. The OAuth connection succeeded and the permissions are correct. Meta is rolling the access flag out per account, and yours is not in the current cohort. There is nothing wrong with your account.

Is the Meta Ads MCP available in New Zealand and Australia? The OAuth flow and the server itself are reachable from NZ and AU, and we have connected accounts from Auckland and Sydney without issue. The actual is_ads_mcp_enabled flag is being flipped account by account, and ANZ accounts appear to be later in the rollout than US accounts. Expect inconsistent results in the short term and broader availability through the second half of 2026.

Do I need Claude Pro or will the free plan work? Custom connectors require Claude Pro or Max. The free Claude plan does not currently support adding custom MCP servers.

Is the Meta Ads MCP free? Meta’s official server is free to use. You will still pay for whichever AI tool you connect it to (Claude Pro, ChatGPT Plus, etc.), but there is no per-account or per-seat charge from Meta.

Can the AI delete or pause my campaigns by accident? On Meta’s official server, new campaigns default to paused status, and most third-party servers behave the same way for safety. The AI will not delete a campaign without your explicit instruction. That said, you should still review every action the AI proposes before approving it. Always.

Where to from here

The Meta Ads MCP is one of those moments where the workflow shifts under your feet. Once you have wired it into Claude or ChatGPT, the way you interact with your ad account changes. You stop clicking through dashboards and start asking questions.

If you are running Meta Ads as part of your business and you want a hand setting up MCP, governance, and the underlying campaign structure, book a call with our team. We work with NZ and AU businesses on paid ads, AI workflows, and the connective tissue between them.

If you are still deciding whether Meta or Google is the right fit for your business, the deeper read is our Google Ads vs Facebook Ads for NZ service businesses post, which covers cost per lead, conversion rate, and lead quality data from real campaigns we have managed.

The official Meta MCP is here. The flag will flip. The teams that have already built the workflow will be the ones that benefit first.