What the error actually means
When you connect the Facebook-hosted Ads MCP at mcp.facebook.com/ads and it returns is_ads_mcp_enabled: false, the OAuth flow worked. Your permissions are correct. Meta itself controls the toggle that decides whether their servers route your tool calls — and you cannot turn it on yourself.
The disabled-reason Meta returns says it plainly:
“Ads MCP is gradually being rolled out. Please check back at a later date to use Ads MCP with this Ad Account.”
Adjacent accounts under the same Business Manager often return different values for the same flag. One advertiser reported seeing an unused personal account enabled while their active business account — verified, with full admin access and a clean compliance record — stayed disabled.
From a recent Pipeboard customer: managing 37 ad accounts across multiple clients, only 8 were enabled for the Facebook-hosted Ads MCP. The other 29 returned the same not-enabled error every time.
Public discussions on r/FacebookAds, advertiser blogs (Lucid Media, Ads Uploader), and Meta’s own help center confirm the rollout is gradual. There is nothing to fix on your side.
Why some accounts and not others
Meta has not published the eligibility rules, and the pattern in the public reports is genuinely strange. Verified businesses in Spain, Brazil, and elsewhere are still waiting; commenters describe accounts they actively use being disabled while empty accounts on the same Facebook profile are enabled; one advertiser with roughly twenty accounts reported only a handful enabled, with the enabled set including ones they don’t use.
The most common public estimate is that around 10% of accounts are enabled as of early May 2026. There is no documented appeal path, no toggle in Business Suite, and no support route that reliably flips the flag.
You wait, or you switch to a tool that does not depend on Meta flipping the flag for you.
Pipeboard works on every Meta account you have access to
Pipeboard is an open-source MCP server for Meta, Google, TikTok, and Snap. Instead of going through Meta’s gated AI-tools surface, it talks directly to the standard Meta Marketing API using your business’ access token. If you can manage an ad account in Ads Manager, Pipeboard can manage it from your AI assistant.
No allowlist, no rollout cohorts, no waiting for Meta to enable a flag. The customer with 37 accounts is now working on all 37.
Comparison reflects publicly documented behavior of mcp.facebook.com/ads as of May 2026.
Why Pipeboard, beyond the rollout
Five ad platforms, not one
Pipeboard covers Meta, Google Ads, TikTok Ads, Snap Ads, and Reddit Ads from the same connection. Meta’s MCP is Meta-only by definition. If your campaigns live on more than one platform, switching to Pipeboard collapses the toolset to one.
120+ write tools, source-available
Create campaigns, ad sets, ads, and creatives. Duplicate winners. Bulk-update budgets. Manage custom and lookalike audiences. Upload images and videos. The Meta MCP server is open on GitHub — you can read every API call before it runs.
Multi-account, multi-client, multi-connection
Connect more than one Meta login (and Google, TikTok, Snap). Per-account API token scoping for agencies. One Pipeboard account can manage every client you work with — without juggling separate sessions.
Read-only mode and per-token scoping
Mint a read-only token for analysis sessions and a separate write-enabled token for execution. Your AI cannot accidentally launch a campaign with the wrong token attached. Token permissions guide.
Badged Meta Business Partner
Pipeboard is a Badged Meta Business Partner — the highest tier in Meta’s partner program, requiring qualifying API spend and verified business identity. See the partner status proof.
Works in every MCP client
Claude (Pro / Max), Claude Code, ChatGPT, Cursor, Windsurf, OpenClaw — plus a CLI for terminal agents. Standard MCP, no vendor lock-in.
Quick setup
- 01Sign up free. Create a Pipeboard account at pipeboard.co/auth/signup. No credit card.
- 02Connect Meta (and any other platform). OAuth into the same Facebook account you use for Business Manager. Add Google, TikTok, and Snap on the same screen if you have them.
- 03Add the MCP URL to your AI client. Copy the per-user URL Pipeboard gives you and paste it into Claude’s custom connector setting (or Cursor’s MCP config, or any other client). See the setup guides for client-specific steps.
- 04Ask your AI to do something. Try: “list my ad accounts”, then “create a new OUTCOME_LEADS campaign in act_XXXX”. No not-enabled errors.
Frequently asked questions
Will Meta eventually enable my account for their MCP?
Probably yes — the rollout is widening over time. Meta has not published a timeline, and there is no way to escalate eligibility from your side. Most advertisers we hear from have been on the wait list for weeks. You can keep the Facebook-hosted connector installed and use Pipeboard in parallel; nothing breaks if Meta enables your account later.
Is Pipeboard a replacement for the Facebook-hosted Ads MCP?
It is an alternative that works on more accounts, more platforms, and more AI clients. If you are already approved by Meta and only need Meta, the Facebook-hosted one is fine. If you want write access on accounts that are not enabled, on Google / TikTok / Snap as well, or want to inspect the source, Pipeboard is the better fit.
How does Pipeboard talk to Meta if not through mcp.facebook.com?
Through the standard Meta Marketing Graph API — the same API every long-running ad tool (Madgicx, Revealbot, Smartly.io, etc.) uses. No special enablement flag is required, only normal access permissions on the ad account.
Is there a free tier?
Yes. The free plan includes 30 AI tool executions per week and supports up to 2 ad accounts. Pro starts at $29.90/mo if you need more.
Can I run my own copy of the server?
Yes. The Meta MCP server is source-available on GitHub. Self-host with your own Meta app credentials if you prefer.
Will Pipeboard change my campaigns without asking?
No. Every change runs through your AI assistant, which asks for confirmation before write operations. You can also restrict Pipeboard to a read-only token for analysis sessions.