Meta Ads MCP Not Enabled? Fixing is_ads_mcp_enabled: false

Updated July 2026.

If the Meta Ads MCP reports is_ads_mcp_enabled: false, your ad account has not yet been included in Meta's gradual rollout — it's a server-side gate, not a configuration mistake you can fix. The other common blocker, redirect_uris are not registered for this client, is an OAuth incompatibility specific to Claude Code's CLI. This page covers both, plus the smaller errors, with verified fixes as of July 2026.

What "is_ads_mcp_enabled": false means

Meta launched its official Ads MCP server (mcp.facebook.com/ads) on April 29, 2026 as a free beta — and it is rolling out account by account. The is_ads_mcp_enabled flag is Meta's per-account toggle. When it reads false, Meta's servers simply won't route MCP tool calls for that ad account, even though your OAuth connection succeeded and the connector appears installed in Claude or ChatGPT.

Key facts about the flag:

• It is controlled entirely by Meta. There is no setting in Ads Manager, Business Manager, or your AI client that flips it.
• Reported rollout order: US accounts first, higher-spend accounts prioritized, with some regions (including parts of the EU and ANZ) still waiting as of mid-2026 — see community rollout tracking.
• There is currently no public request form or early-access program to verify. Treat any service promising to "enable" the flag for you with suspicion.

Fix checklist for is_ads_mcp_enabled: false

1. Confirm it's the flag, not your connection. If the connector authenticated and tools are listed, but calls fail with is_ads_mcp_enabled: false, the connection is fine — you're gated.
2. Check which Meta profile you authorized. The flag applies per ad account. If your login can access several accounts, retry against each — rollout can differ between accounts under the same Business Manager.
3. Verify your ad account role. You need admin or full advertiser access on the ad account you're targeting; a personal profile without business access will fail earlier, but partial access produces confusing states.
4. Try a higher-spend or US-based account if you manage several. This is the clearest verified pattern in who has access.
5. Reconnect and retry periodically. Accounts are being enabled continuously through the beta. Disconnect the connector, reconnect, and re-test every week or two.
6. If you can't wait, choose interim tools carefully. Third-party Meta MCP servers exist, but most route calls through a shared developer app, which carries real risk — read is Meta Ads MCP safe? before you pick one.

"The provided redirect_uris are not registered for this client"

This error appears when you add mcp.facebook.com/ads to Claude Code (the CLI) and it attempts OAuth. It is tracked in multiple open issues on the Claude Code repository, including issue #55002.

Cause: Claude Code's MCP client uses dynamic client registration with a localhost loopback redirect (e.g. http://localhost:<port>/callback) — the standard pattern for HTTP MCP servers. Meta's OAuth client for the Ads MCP only accepts specific pre-registered redirect URIs, so the handshake is rejected before you ever see a login screen.

Verified fixes:

1. Connect from claude.ai (web) or Claude Desktop instead. Both use redirect URIs Meta has whitelisted, and users consistently report the same connector authenticating fine there.
2. Don't fight it in the CLI. As of July 2026 there is no user-side workaround documented in the GitHub issues; the fix has to come from the Meta/Anthropic OAuth configuration.

Other Meta Ads MCP errors worth checking

• Connector worked, then stopped after ~2 months. Meta access tokens last roughly 60 days and don't auto-refresh in every client. Disconnect and reconnect the connector to mint a fresh token.
• Tools don't appear in your AI client. Remove the connector, restart the client, and re-add https://mcp.facebook.com/ads. Custom remote connectors also generally require a paid Claude or ChatGPT plan.
• Wrong account answered. If prompts return data for an unexpected account, specify the ad account ID explicitly in your prompt, and check which profile you used at the OAuth step.
• Rate-limit errors on big accounts. Standard-access accounts are throttled under Meta's Marketing API rate limits — community testing puts the practical ceiling around 200 calls per hour. Ask for smaller date ranges and fewer breakdowns per question.

Meta Ads MCP rollout status (July 2026)

The Ads MCP remains a free beta with gradual, Meta-controlled enablement. What's verifiable now: the server launched April 29, 2026; setup is documented in the Meta Business Help Center for Claude, ChatGPT, and Perplexity; and access continues to expand account by account, with no self-serve enablement. If your account is gated, waiting genuinely is the primary fix.

While you wait — or after you connect — remember what the MCP won't do even when enabled: it doesn't watch your account between sessions, doesn't keep a change history, and forgets everything when the chat ends. The Ad Spend covers that persistent layer: checks roughly every 6 hours with 1,900+ detection algorithms, a permanent record of every change (who, what, when), and Slack alerts the moment something moves. It connects by OAuth with no API keys and no rollout waitlist, and it works alongside any MCP setup — here's how the two layers fit together.

FAQ

How do I enable is_ads_mcp_enabled for my ad account?

You can't. The flag is set by Meta as part of a gradual beta rollout. There is no setting, form, or support path that verifiably flips it — reconnecting periodically to re-check is the only real action available.

Why does the Meta Ads MCP work in Claude Desktop but not Claude Code?

Claude Code's CLI uses dynamic client registration with a localhost redirect URI, which Meta's OAuth client doesn't accept — producing "The provided redirect_uris are not registered for this client." Claude.ai web and Claude Desktop use whitelisted redirects and authenticate normally.

How long does the Meta Ads MCP rollout take?

Meta hasn't published a timeline. The observable pattern since the April 29, 2026 launch is US-first and higher-spend-first, with enablement continuing through mid-2026.

My connector stopped working after two months. Why?

Most likely an expired access token — Meta tokens last roughly 60 days and not every client refreshes them automatically. Disconnect and reconnect the connector.