Meta Ads MCP OAuth Works But Most Ad Accounts Not Enabled Yet

A Reddit user attempting to use Meta's Ads MCP server with Claude Desktop reports that OAuth authentication completes successfully and all 29 tools load without errors. However, calling ads_get_ad_accounts returns a JSON response indicating the ad account is not yet enabled for Ads MCP:

{
  "is_ads_mcp_enabled": false,
  "is_ads_mcp_disabled_reason": "Ads MCP is gradually being rolled out. Please check back at a later date to use Ads MCP with this Ad Account."
}

The user is asking if anyone has actually been enabled, and whether there are specific actions that might get prioritized — such as submitting a form, business verification status, or account spend history. They note they couldn't find a beta interest form that actually does anything.

This is a common early-access rollout pattern: the MCP server infrastructure is live and authentication works, but feature flags on the backend gate individual ad accounts. If you hit this same response, there's no workaround yet — Meta appears to be expanding access over time without a public signup form.

For now, developers integrating with Meta Ads should plan for a manual fallback (e.g., using the Ads API directly) until their account is enabled. Keep an eye on is_ads_mcp_disabled_reason for updates — if Meta changes the reason message or enables your account, the same endpoint will reflect that.