Traffic light showing red against a plain teal sky

MCP servers

Why does Meta's ads MCP say is_ads_mcp_enabled: false for my ad account, and how do I get it turned on?

By The Tofu team ·

Meta doesn't document is_ads_mcp_enabled: false. Pipeboard, which sells its own Meta ads MCP server, says it means Meta's server isn't turned on for that ad account yet, even though you connected. Meta says it is "gradually rolling out access to tools available to ad accounts," and it publishes no criteria, date or way to ask for access, so there's no documented way to switch it on yourself. Checking your access, permissions and account status is still worth it, though Meta doesn't say any of them controls the flag. Meanwhile, use an enabled ad account, Ads Manager or the Marketing API.

As of October 2026.

What does is_ads_mcp_enabled: false mean?

According to Pipeboard, which sells its own Meta ads MCP server, it means the ads MCP server isn't turned on for that ad account yet, even though you are connected. Meta doesn't document the flag on any developer or help page we found. Pipeboard reports the message that comes with it as "Ads MCP is gradually being rolled out. Please check back at a later date to use Ads MCP with this Ad Account," and says it is not a permissions problem. That matches what Meta's developer blog said on July 16, 2026: "we'll be gradually rolling out access to tools available to ad accounts through this integration method."

Which ad accounts can use Meta's ads MCP server?

Meta doesn't say which accounts get it first. It announced the server in open beta on April 29, 2026, "built for businesses of all sizes across regions," and its help article still warns, "You may not have access to all of these tools and features yet." The requirements Meta does document are about access, not the account:

  • A Facebook account or Meta Managed Account with access to the ad account.
  • With your own token: ads_mcp_management plus ads_read or ads_management. Only Employee-role system user tokens work; Admin-role ones "can't access the ads MCP server."
  • With your own Meta app that manages other businesses' accounts: Advanced Access to ads_mcp_management through App Review.

Meta names no spend level, account age, region or verification requirement. For setup itself, see what Meta's ads MCP server is and how to connect it.

Can I turn it on myself or ask Meta to enable it?

Not by any route Meta documents. Meta lists no setting, form or support route that enables an ad account. The Ads MCP server page in Meta Business Suite settings sets rules for what agents may do; it doesn't enable accounts, and Meta says that if you don't see it, "you don't have access to this feature yet." Pipeboard says that page shows a dash for accounts that are still waiting; Meta doesn't document that.

Do business verification, account status or my role matter?

They matter for other reasons, but Meta doesn't link any of them to the flag. Here is what Meta does document:

What people checkWhat Meta documents
Business verificationRequired "if your app will access sensitive data," for developers using their own Meta app. Not listed for the ads MCP server
Account statusA restricted ad account can lose features or the ability to advertise. Check it in Business Support Home under Account status overview
Your roleYou need access to the ad account. Ask the agent to list your ad accounts: Meta's ads_get_ad_accounts tool returns each one's name and status
Read or ManageEach connected app's scope is set in your Facebook account's Business Integrations settings. Read limits the agent to reading; Meta doesn't connect it to the flag

Why is it on for my unused ad accounts but not my main one?

Meta hasn't explained the order. Pipeboard says the order is "hard to predict" and that people report idle accounts enabled while their main, high-spend account still waits. Meta doesn't say whether a new ad account would be enabled sooner. If your main account is restricted, don't open new ones to get around it: Meta treats creating new accounts "with the intent to repeat violations" as evading enforcement.

Claude connects but can't use my business ad account. Why?

The account may not be enabled yet, or it may not have been shared when you signed in. Pipeboard says the Meta login asks you to choose which ad accounts to share, so disconnect, reconnect and select the missing account. If the account appears in the agent's account list but returns is_ads_mcp_enabled: false, that points to the rollout. If it doesn't appear at all, check that the Facebook profile you signed in with has access to it in your business portfolio.

Why do I get "Internal error" when creating an ad set?

Meta hasn't documented this error for the ads MCP server. In its Marketing API error list, Meta says negative error codes "are internal Facebook errors" and to "check error_subcode for the actual failure code." So:

  1. Ask the agent for the full error, including the code and subcode.
  2. Ask it to run ads_get_errors, which Meta says returns "delivery-blocking errors" for campaigns, ad sets, ads or an ad account.
  3. Check for a rule that blocks creating ad sets. If any actions are blocked, the Ads MCP server page in Business Suite settings shows Limited next to Take actions in this ad account.
  4. Build the same ad set in Ads Manager to see the plain-language message.

Meta's error list names several ad set blockers you can rule out:

CodeMeta's description
200, subcode 1870034"You'll need to agree to the Custom Audience terms before you can create or edit an audience or an ad set"
1870092"To create or edit audience or ad set, please agree to the Meta Business Tools terms"
2446394The ad set includes detailed targeting options that are "no longer available"
1885272"Budget is too low"

What is error subcode 1815089 on lead ads?

Meta's public Marketing API error list doesn't include it. LeadSync, a lead-sync vendor, says #1815089 reads "Terms of service not accepted: You can't run lead ads until your Facebook Page accepts Facebook's Lead Generation Terms of Service." Meta's help center states the requirement LeadSync points to: "you must review and accept the Lead Ads Terms," and "If you run lead ads on multiple Facebook Pages, you must accept the Lead Ads Terms for each Page." Meta's list of ads MCP tools has none for lead forms or terms, so accept them in Meta at facebook.com/ads/leadgen/tos (the link in Meta's help article), for the Page behind the ad, then have the agent try again. LeadSync says only a Page admin can accept.

What can I use until Meta enables my account?

You have three options. Use an ad account that is already enabled, if you have one. Use Ads Manager directly, where Meta offers its Meta AI business assistant. Or use the Marketing API through your own Meta app, or a third-party MCP server built on it: Pipeboard says its server "does not depend on Meta's rollout." Before you connect any agent, read whether connecting an AI agent can get your Meta ad account banned.

Sources

Related answers

More on

Let an agent build your next campaign.

Tofu Ads Agent reads your CRM, plans the funnel, builds the audience and creative, and stages full campaigns across LinkedIn, Google and Meta for your approval.

Try it free Get a demo