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.
📖 Read the full source: r/ClaudeAI
👀 See Also
ClawVibe: A Hands-Free iOS Voice Assistant for AI Agents with On-Device STT/TTS
ClawVibe is a native iOS app that provides hands-free voice interaction with AI agents during commutes. It uses on-device speech recognition and TTS, supports CarPlay, and includes voice biometrics to filter background noise. Only text is sent over the network.
The Human Creativity Benchmark: Separating Convergence from Divergence in AI Creative Evaluation
Contra Labs introduces the Human Creativity Benchmark (HCB), a framework that distinguishes objectively verifiable criteria (e.g., prompt adherence) from subjective taste (e.g., visual appeal) in evaluating generative AI for creative work. The benchmark reveals that no current model is reliably both correct and steerable, addressing mode collapse and the need for differentiated output.
Quiver: A GUI for Managing and Syncing Claude Code Skills
Quiver is a free, open-source GUI tool that provides a web interface for managing Claude Code skills, allowing users to browse local skills and marketplace plugins, edit SKILL.md files, sync via Git, and install skills without using the terminal.
Open-Sourced the-vibe-stack: Markdown Rules to Maintain Claude Code Consistency
A developer has open-sourced 'the-vibe-stack' — a set of Markdown rules designed to keep Claude Code on track during long sessions by enforcing a rigid schema. The approach aims to reduce logic drift and token waste while ensuring predictable output.